[Desktop-packages] [Bug 513358] Re: Weather applet is missing several important Lithuanian locations (cities)
** Changed in: libgweather Importance: Medium => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/513358 Title: Weather applet is missing several important Lithuanian locations (cities) Status in libgweather: New Status in “libgweather” package in Ubuntu: Triaged Status in Baltix GNU/Linux: New Bug description: Weather applet in Ubuntu Lucid (and older) hasn't several important Lithuanian cities :( According to http://live.gnome.org/LibGWeather/ImprovingLocations I should provide the complete list of Lithuanian major cities, which should be added into /data/major-cities.txt from libgweather sources instead of patching Locations.xml So, I'm providing the complete list of Lithuanian major cities. This list contains capitals of provinces (countries) and 2 important (very popular) resort/spa towns, see http://en.wikipedia.org/wiki/Lithuania#Largest_cities , http://en.wikipedia.org/wiki/Counties_of_Lithuania , http://en.wikipedia.org/wiki/Druskininkai and http://www.geonames.org/LT/largest-cities-in-lithuania.html I've already reported this bug to https://bugzilla.gnome.org/show_bug.cgi?id=608039 , but I'm also reporting here, to be sure, that Ubuntu 10.04 LTS will have all Lithuanian major cities in Weather applet. # Lithuania. Source: http://en.wikipedia.org/wiki/Lithuania#Largest_cities and # http://en.wikipedia.org/wiki/Druskininkai # FIPS-code [Latitude] [Longitude] Level Name [ # comment ] LH54.68325.3173Vilnius # Vilnius LH54.90023.9002Kaunas # Kaunas LH55.71721.1182Klaipėda # Klaipeda LH55.93323.3172Šiauliai # Siauliai LH55.73324.3502Panevėžys # Panevezys LH54.40024.0502Alytus # Alytus LH54.56723.3502Marijampolė # Marijampole LH55.25022.2832Tauragė # Taurage LH55.98322.2502Telšiai # Telsiai LH55.50025.6002Utena # Utena LH55.91721.0692Palanga # Klaipeda LH54.01723.9672Druskininkai # Alytus To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/513358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236965] Re: pulseaudio does not recognize internal speakers [P180HMx, Realtek ALC892, Speaker, Internal] volume slider problem
if (cfg->line_out_type != AUTO_PIN_SPEAKER_OUT) {
err = try_assign_dacs(codec, cfg->speaker_outs,
cfg->speaker_pins,
spec->multiout.extra_out_nid,
spec->speaker_paths,
spec->extra_out_badness);
if (err < 0)
return err;
+if (cfg->speaker_outs != 3)
badness += err;
}
external 5.1 (channel mode switch) seem can be enabled in hda-emu by ignoring
extra out badness when there are three internal speakers
"Speaker Surround Playback Volume" and "Speaker CLFE" changed to "Surround
Playback Volume", "Center Playback Volume" and "LFE Playack Volume"
"PCM playback Volume" and "PCM playback Switch" change to "Front Playback
volume" and "Front Playback Switch"
what's missing is the external 7.1 ( using headphone jack)
autoconfig: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
speaker_outs=3 (0x14/0x16/0x15/0x0/0x0)
hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
mono: mono_out=0x0
dig-out=0x1e/0x0
inputs:
Internal Mic=0x12
Mic=0x18
Line=0x1a
==> Best config: lo_type=0, wired=0, mio=1
multi_outs = 17/0/0/0 : 5/2/3/0 (type LO)
out path: depth=3 :05:0f:17
multi_ios(2) = 1a/18 : 2/3
mio path: depth=3 :02:0c:1a
mio path: depth=3 :03:0d:18
hp_outs = 1b/0/0/0 : 4/0/0/0
hp path: depth=3 :04:0e:1b
spk_outs = 14/16/15/0 : 0/0/3/0
spk path: depth=3 :03:0d:15
CTRL: add: Channel Mode:0
CTRL: add: Front Playback Volume:0
CTRL: add: Front Playback Switch:0
CTRL: add: Surround Playback Volume:0
CTRL: add: Surround Playback Switch:0
CTRL: add: Center Playback Volume:0
CTRL: add: LFE Playback Volume:0
CTRL: add: Center Playback Switch:0
CTRL: add: LFE Playback Switch:0
CTRL: add: Headphone Playback Volume:0
CTRL: add: Headphone Playback Switch:0
CTRL: add: Speaker CLFE Playback Switch:0
CTRL: add: Line Out Jack:0
JACK created Line Out, type 4
JACK report Line Out, status 0
CTRL: add: Headphone Jack:0
JACK created Headphone, type 1
JACK report Headphone, status 0
CTRL: add: Speaker Front Phantom Jack:0
CTL Notify: Speaker Front Phantom Jack:0, mask=1
CTRL: add: Speaker Surround Phantom Jack:0
CTL Notify: Speaker Surround Phantom Jack:0, mask=1
CTRL: add: Speaker CLFE Phantom Jack:0
CTL Notify: Speaker CLFE Phantom Jack:0, mask=1
--
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/1236965
Title:
pulseaudio does not recognize internal speakers [P180HMx, Realtek
ALC892, Speaker, Internal] volume slider problem
Status in “linux” package in Ubuntu:
Fix Committed
Status in “pulseaudio” package in Ubuntu:
In Progress
Bug description:
steps to reproduce:
1. acquire a device with the problem, such as Clevo P180HM laptop
motherboard
2. install ubuntu 12.04 (now updated to 12.04.3 currently)
3. systray > speaker-icon > sound-settings > output tab
4. no entry for "speakers built-in audio" appears
workaround:
running the shell script mentioned in this comment helps --
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/comments/158
however, the workaround is not completely satisfactory, because
adjusting the (singular) volume-slider provided by pulseaudio only
causes some of the (multiple) volume-sliders known to alsamixer to react.
Specifically, turning the pulseaudio volume upwards only changes the
'master' and belatedly the 'pcm' volumes inside alsamixer. This ignores
'speaker clfe' + 'speaker front' + 'speaker surround playback volume'
plus maybe others. Effectively, this means audio playback is weak: instead
of spreading typical 2ch audiofiles across all internal speakers, only some
are used, and only at whatever volume alsamixer specifies. (Turning the
ignored volumes up in alsamixer causes a different problem: then it is no
longer possible to lower the sound to a relatively-quiet volume.)
Here is some information from one of the ubuntu pulseaudio/alsa devs:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/comments/159
David Henningsson (946...@bugs.launchpad.net) wrote:
...you have unusual hardware: in addition to normal
headphones and stereo line out, you have 5.1 internal speakers. This
leads to unusual alsamixer names (e g "Speaker Front") which we do not
match for in PulseAudio. Fixing that means that we should add those
names in PulseAudio - but let's discuss that in a new bug instead.
Let me know if you would like more specifics. I have run codecgraph,
alsa-info, etc.
$ cat /proc/asound/card*/codec#* | grep --before-context=4 --after-context=1
"Subsystem Id"
Codec: Realtek ALC892
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0892
Subsystem Id: 0x15588000
Revision Id: 0x100302
--
Codec: ATI R6xx HDMI
Address: 0
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x1002aa01
Subsystem Id: 0x
[Desktop-packages] [Bug 1240387] [NEW] no user defined gui buttons anymore
Public bug reported: The older version of evince (in raring) offered the possibility to have user defined buttons for frequently used operations (like, in my case, rotate left, rotate right, save as). This feature is now gone. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 16 09:31:17 2013 InstallationDate: Installed on 2011-04-05 (924 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True SourcePackage: evince UpgradeStatus: Upgraded to saucy on 2013-10-15 (0 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1240387 Title: no user defined gui buttons anymore Status in “evince” package in Ubuntu: New Bug description: The older version of evince (in raring) offered the possibility to have user defined buttons for frequently used operations (like, in my case, rotate left, rotate right, save as). This feature is now gone. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 16 09:31:17 2013 InstallationDate: Installed on 2011-04-05 (924 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True SourcePackage: evince UpgradeStatus: Upgraded to saucy on 2013-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1240387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
https://code.launchpad.net/ubuntu/+source/alsa-driver the modified date seem freeze at Feb/2013 -- 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/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in The Linux Kernel: New Status in “alsa-driver” package in Ubuntu: Triaged Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX 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.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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/alsa-driver/+bug/1166529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236752] Re: gnome-settings-daemon (3.4.2-0ubuntu0.6.3) breaks nvidia multi-monitor-config
gnome-settings-daemon version 3.4.2-0ubuntu0.6.4 fixes my problem. Thank you for your help! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1236752 Title: gnome-settings-daemon (3.4.2-0ubuntu0.6.3) breaks nvidia multi- monitor-config Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Precise: Fix Committed Bug description: [ Description ] The fix for bug #1065979 regresses multi-monitor behaviour for some users. [ Fix ] Revert it. [ Regression potential ] This will undo any fix for bug #1065979. But we promise that we won't *introduce* bugs in stable release updates, so this has to take priority. The contributor of the fix to that bug can try again if desired, but probably with an extended ageing period in -proposed. [ Original report ] Hello, I use Kubuntu 12.04.x with lightdm as login-manager to KDE and the nvidia binary driver with 2 monitors (DVI, TwinView). My Multi-Monitor config: right monitor: MAIN monitor left monitor: second monitor as extension: with mode left of Main Monitor This config is setup with nvidia-settings, which stores in xorg.conf and in .nvidia-settings in home-dir. In KDE the config is also stored with krandr as default config. After upgrading from package gnome-settings-daemon (3.4.2-0ubuntu0.6.2) to gnome-settings-daemon (3.4.2-0ubuntu0.6.3), the xorg.conf settings are ignored/misinterpreted as well as the KDE krandr settings. When lightdm is started, the second monitor is on the right side, and when logging-in to KDE either clone mode on both monitors is started or the second monitor is on the right side (mirrored). => I have to set my desired settings manually again and at the next reboot the problem persists. I have downgraded to gnome-settings-daemon-3.4.1-0ubuntu1, and the problem is gone. All fine again. I didn't find the previous version 3.4.2-0ubuntu0.6.2. How can I get this package version? Faulty package/patch: gnome-settings-daemon (3.4.2-0ubuntu0.6.3) precise; urgency=low * debain/patches/follow-lid.patch: - external/internal monitors mirrored on boot when laptop lid is closed (lp: #1065979) -- Ritesh Khadgaray Tue, 13 Aug 2013 11:29:20 +0530 1065979 external/internal monitors mirrored on boot when laptop lid is closed I use this PC at my workplace, so it is important for me to solve this problem. Thank you for your help! Best regards, Bernhard lsb_release -rd Description:Ubuntu 12.04.3 LTS Release:12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50 Uname: Linux 3.2.0-54-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Tue Oct 8 10:29:18 2013 EcryptfsInUse: Yes InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True ProcEnviron: LANGUAGE=de_AT TERM=xterm PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1236752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1132803] Re: Ghostscript crashes opening corrupted pdf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ghostscript (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1132803 Title: Ghostscript crashes opening corrupted pdf Status in “ghostscript” package in Ubuntu: Confirmed Bug description: If ghostscript opens a corrupted pdf file, it will produce endless syslog entrys: file has unbalanced q/q operators (too many q's) Ghostscript never stop writing to syslog, until harddisk is full. This bug can be fixed by following this diff: http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=3a56f4eb5a9f15795725374b297edab0fb8ebc5d My System is: Ubuntu 12.04.2 Server 64-Bit Ghostscript Version: 9.05~dfsg-0ubuntu4.2 Could you please apply this diff? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1132803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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]
(In reply to comment #112) > Just a few remarks. > I still see this bug with Kernel 3.8, Mesa 9.2.1 and DRI 2.99.904. > Moreover, with switching from Mesa 9.1.x to Mesa 9.2.x the number of lockups > highly increased (especially in games). On snb the blorp engine in mesa has become a bit more hang-happy, see bug #70151 Not all gpu hangs are created equal ;-) > Additionally with running the latest drivers complete system lockups are > gone, but it's still a lockup for multiple seconds with following VT > switching. You mean a gpu hang happens while when doing a vt switch? -- 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 1237564] Re: Regression: some previous keyboard bindings & all newly created custom bindings fail if gnome-screensaver isn't installed
Uploaded to saucy-proposed. It'll probably miss the release but should get in as a stable update, hopefully. ** Description changed: + [ Description ] + + gnome-settings-daemon 3.8.5-0ubuntu7 used the presence of + org.gnome.ScreenSaver on the session bus to decide whether to activate + the media keys plugin (used for volume up/down, skipping tracks, + brightness and so on). + + This package is only a Recommends of ubuntu-desktop. It's an undeclared + dependency which isn't actually necessary. + + [ Proposed fix ] + + Check for org.gnome.Panel (for gnome-panel environments) and + com.canonical.Unity (for Unity environments). Unity also provides + org.gnome.Shell so check $DESKTOP_SESSION in that handler to only run in + a real gnome-shell session. + + [ Test case ] + + Remove the gnome-screensaver package. In a gnome-panel based or a Unity + session, launch gnome-settings-daemon. Make sure your media keys work + with the update. + + [ Regression potential ] + + This changes activation of a plugin. There's a chance it could be wrong. + + If it doesn't work, make sure the plugin is enabled: + + $ gsettings get org.gnome.settings-daemon.plugins.media-keys active + + and then run + + $ gnome-settings-daemon --debug --replace | tee /tmp/g-s-d.log + + wait 5 seconds, try pressing some media keys, then attach /tmp/g-s-d.log + + [ Original report ] + With the latest g-s-d any custom key-bindings fail as do some 'default* ones (system Test cases - remove gnome-screensaver open keyboard panel > shortcuts> system change Log out to a new binding log out/in thru indicator-session Try the new binding, nothing happens open keyboard panel > shortcuts> custom create a new binding for some command log out/in use binding, nothing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 9 14:03:35 2013 InstallationDate: Installed on 2013-10-03 (6 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) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-settings-daemon (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- 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/1237564 Title: Regression: some previous keyboard bindings & all newly created custom bindings fail if gnome-screensaver isn't installed Status in “gnome-settings-daemon” package in Ubuntu: In Progress Bug description: [ Description ] gnome-settings-daemon 3.8.5-0ubuntu7 used the presence of org.gnome.ScreenSaver on the session bus to decide whether to activate the media keys plugin (used for volume up/down, skipping tracks, brightness and so on). This package is only a Recommends of ubuntu-desktop. It's an undeclared dependency which isn't actually necessary. [ Proposed fix ] Check for org.gnome.Panel (for gnome-panel environments) and com.canonical.Unity (for Unity environments). Unity also provides org.gnome.Shell so check $DESKTOP_SESSION in that handler to only run in a real gnome-shell session. [ Test case ] Remove the gnome-screensaver package. In a gnome-panel based or a Unity session, launch gnome-settings-daemon. Make sure your media keys work with the update. [ Regression potential ] This changes activation of a plugin. There's a chance it could be wrong. If it doesn't work, make sure the plugin is enabled: $ gsettings get org.gnome.settings-daemon.plugins.media-keys active and then run $ gnome-settings-daemon --debug --replace | tee /tmp/g-s-d.log wait 5 seconds, try pressing some media keys, then attach /tmp/g-s-d.log [ Original report ] With the latest g-s-d any custom key-bindings fail as do some 'default* ones (system Test cases - remove gnome-screensaver open keyboard panel > shortcuts> system change Log out to a new binding log out/in thru indicator-session Try the new binding, nothing happens open keyboard panel > shortcuts> custom create a new binding for some command log out/in use binding, nothing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 9 14:03:35 2013 InstallationDate: Installed on 2013-10-03 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002) MarkForU
[Desktop-packages] [Bug 1231841] Re: lightdm crashed with SIGABRT in _g_log_abort()
** Branch linked: lp:ubuntu/saucy-proposed/lightdm -- 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/1231841 Title: lightdm crashed with SIGABRT in _g_log_abort() Status in Light Display Manager: Fix Committed Status in “lightdm” package in Ubuntu: In Progress Bug description: Lightdm continue to crash on my two systems. Ati and Nvidia. Usually every 2 or 3 boot lightdm doesn't start. This is very very annoying please fix this issue. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Thu Sep 26 22:20:20 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-09-22 (4 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130905) MarkForUpload: True ProcCmdline: lightdm restart Signal: 6 SourcePackage: lightdm StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_filename_display_name () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: lightdm crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1231841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to ctrl+shift
Confirmed under Ubuntu Saucy (of today, through the daily iso images). -- 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/1218322 Title: Can't set keyboard layout change to ctrl+shift Status in Indicator keyboard: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1230148] Re: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()
** Branch linked: lp:ubuntu/saucy-proposed/network-manager-applet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1230148 Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() Status in “network-manager-applet” package in Ubuntu: In Progress Bug description: After logging back in from a mir test session (installed unity-system- compositor, reboot, play with mir a bit, remove mir from lightdm startup, reboot). ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: network-manager-gnome 0.9.8.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sun Sep 22 11:22:01 2013 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-23 (63 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.254 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.64 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet SegvAnalysis: Segfault happened at: 0x7f4e8813aa4c : cmp%rax,(%rdx) PC (0x7f4e8813aa4c) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: network-manager-applet StacktraceTop: gtk_status_icon_set_visible () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libappindicator3.so.1 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() UpgradeStatus: Upgraded to saucy on 2013-07-27 (59 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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-applet/+bug/1230148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196921] Re: updating packages to lua5.2 in main
Deferring the rest of this bug until T. ** Changed in: graphviz (Ubuntu Saucy) Status: In Progress => Won't Fix ** Changed in: graphviz (Ubuntu Saucy) Milestone: ubuntu-13.10 => None ** Changed in: graphviz (Ubuntu) Milestone: None => ubuntu-13.10 ** Changed in: ibus-pinyin (Ubuntu Saucy) Status: In Progress => Won't Fix ** Changed in: ibus-pinyin (Ubuntu Saucy) Milestone: ubuntu-13.10 => None ** Changed in: ibus-pinyin (Ubuntu) Milestone: None => ubuntu-13.10 ** Changed in: lua5.1 (Ubuntu Saucy) Status: Confirmed => Won't Fix ** Changed in: lua5.1 (Ubuntu Saucy) Milestone: ubuntu-13.10 => None ** Changed in: lua5.1 (Ubuntu) Milestone: None => ubuntu-13.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-pinyin in Ubuntu. https://bugs.launchpad.net/bugs/1196921 Title: updating packages to lua5.2 in main Status in “graphviz” package in Ubuntu: In Progress Status in “ibus-pinyin” package in Ubuntu: In Progress Status in “libquvi” package in Ubuntu: Fix Released Status in “lua5.1” package in Ubuntu: Confirmed Status in “lua5.2” package in Ubuntu: Fix Released Status in “rrdtool” package in Ubuntu: Fix Released Status in “rubyluabridge” package in Ubuntu: Fix Released Status in “vim” package in Ubuntu: Fix Released Status in “graphviz” source package in Saucy: Won't Fix Status in “ibus-pinyin” source package in Saucy: Won't Fix Status in “libquvi” source package in Saucy: Fix Released Status in “lua5.1” source package in Saucy: Won't Fix Status in “lua5.2” source package in Saucy: Fix Released Status in “rrdtool” source package in Saucy: Fix Released Status in “rubyluabridge” source package in Saucy: Fix Released Status in “vim” source package in Saucy: Fix Released Bug description: promoted today lua5.2 to main. This leaves us with both 5.1 and 5.2 in main. 5.1 should be dropped for the 13.10 release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/1196921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1155825] Re: [printers]: gnome-control-center crashed with SIGABRT in __libc_message()
** Branch linked: lp:ubuntu/saucy-proposed/gnome-control-center -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1155825 Title: [printers]: gnome-control-center crashed with SIGABRT in __libc_message() Status in GNOME Control Center: Fix Released Status in “gnome-control-center” package in Ubuntu: In Progress Bug description: just tried to add a HP LazerJet 5 printer which is already up & running on all my other Linux Distros ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu15 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic i686 ApportVersion: 2.9.1-0ubuntu1 Architecture: i386 Date: Fri Mar 15 18:28:10 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-03-15 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha i386 (20130313) MarkForUpload: True ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: [printers]: gnome-control-center crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1155825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1189058] Re: Dash: com.canonical.Unity.Lenses should have a key to individually disable online/remote searches per scope id
Marking invalid, because this functionality is already part of Ubuntu 13.10, see comment #5! ** Changed in: ayatana-design Status: Confirmed => Invalid ** Changed in: unity-scope-home Status: Confirmed => Invalid ** Changed in: unity (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1189058 Title: Dash: com.canonical.Unity.Lenses should have a key to individually disable online/remote searches per scope id Status in Ayatana Design: Invalid Status in Unity Home Scope: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: As it stands now you only have "remote-content-search" 'all or 'none' That seems overly permissive or restrictive Users should have the choice to allow some scopes to do remote searches & disallow others as they see fit. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.0daily13.06.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic i686 ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Jun 8 20:58:06 2013 InstallationDate: Installed on 2013-05-29 (10 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130529) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1189058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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]
(In reply to comment #113) > On snb the blorp engine in mesa has become a bit more hang-happy, see bug > #70151 > Not all gpu hangs are created equal ;-) > Actually it was on Sandybridge. > You mean a gpu hang happens while when doing a vt switch? No I meant, if you suffer a lockup you just have to wait a few seconds and switch to another VT and back, then you can resume with your system (although sometimes fonts are broken). -- 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 1240425] [NEW] WPA network connection always triggers password confirmation
Public bug reported: Every time I boot or resume my machine at the office, where there is a WPA network, I am prompted for the authentication details and forced to connect manually. The username and password are automatically filled in from the last successful attempt, and clicking 'connect' is successful. However, this reveals an underlying bug, probably to do with the consistent failure of the first connection attempt owing to timeouts being hit (extra startup time when first initialised?) This may have the same underlying cause as https://bugs.launchpad.net/wicd/+bug/1084380 and https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1084364 that wpa_supplicant takes a while to connect, and network-manager doesn't appreciate that it needs more time under certain circumstances, like the first connection attempt. Fixing this will make ubuntu MUCH BETTER for many many people I suspect, where they are permanently struggling with no network and a popup window where no such failure was necessary - e.g. the network and adapter are all fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Wed Oct 16 10:12:19 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.32.78.1 dev wlan0 proto static 10.32.78.0/23 dev wlan0 proto kernel scope link src 10.32.78.87 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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 enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug gnome3-ppa i386 saucy third-party-packages -- 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/1240425 Title: WPA network connection always triggers password confirmation Status in “network-manager” package in Ubuntu: New Bug description: Every time I boot or resume my machine at the office, where there is a WPA network, I am prompted for the authentication details and forced to connect manually. The username and password are automatically filled in from the last successful attempt, and clicking 'connect' is successful. However, this reveals an underlying bug, probably to do with the consistent failure of the first connection attempt owing to timeouts being hit (extra startup time when first initialised?) This may have the same underlying cause as https://bugs.launchpad.net/wicd/+bug/1084380 and https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1084364 that wpa_supplicant takes a while to connect, and network-manager doesn't appreciate that it needs more time under certain circumstances, like the first connection attempt. Fixing this will make ubuntu MUCH BETTER for many many people I suspect, where they are permanently struggling with no network and a popup window where no such failure was necessary - e.g. the network and adapter are all fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Wed Oct 16 10:12:19 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.32.78.1 dev wlan0 proto static 10.32.78.0/23 dev wlan0 proto kernel scope link src 10.32.78.87 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/fr
[Desktop-packages] [Bug 1226197] Re: Network menu shows WiFi networks even the switch is off
OK, so. the wifi-enabled switch needs a bit love. Currently it gets it's state changed when NM sends wifi-enabled signal, but also when wifi device changes state. -- 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/1226197 Title: Network menu shows WiFi networks even the switch is off Status in Network Menu: Incomplete Status in “network-manager” package in Ubuntu: Confirmed Bug description: I reboot my phone and the network menu shows wireless networks even though the wifi switch indicates that its disabled. I have attached a screenshot. Its pretty easily reproducible here. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-network 0.5.0+13.10.20130913-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.1-0ubuntu4 Architecture: armhf Date: Mon Sep 16 18:43:04 2013 InstallationDate: Installed on 2013-09-14 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130914.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1226197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240428] [NEW] Radeon drivers not loaded properly after upgrading to Saucy
Public bug reported: After upgrading to Ubuntu 13.10 (Saucy), GDM stops to work (strange colors appearing on screen), and lightdm works using llvmpipe instead of radeon drivers. Performance is really bad and dual screen no longer works. It worked perfectly before upgrading. When loging to the session a message box appears saying "System program problem detected". Unfortunately when I click to "Send report..." nothing happens. The display box disappears automatically after some time. Among other things, I tried to purge all radeon-related packages and reinstalling them again, with no success. Any idea? Thank you very much Output of glxinfo | grep Gallium: OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) Output of dmesg | egrep 'drm|radeon' [ 16.400055] [drm] Initialized drm 1.1.0 20060810 [ 17.543444] [drm] radeon kernel modesetting enabled. [ 17.543878] [drm] initializing kernel modesetting (RV610 0x1002:0x94C1 0x1028:0x0D02). [ 17.543892] [drm] register mmio base: 0xFE9F [ 17.543893] [drm] register mmio size: 65536 [ 17.543971] radeon :01:00.0: VRAM: 256M 0x - 0x0FFF (256M used) [ 17.543973] radeon :01:00.0: GTT: 512M 0x1000 - 0x2FFF [ 17.543975] [drm] Detected VRAM RAM=256M, BAR=256M [ 17.543976] [drm] RAM width 64bits DDR [ 17.544046] [drm] radeon: 256M of VRAM memory ready [ 17.544047] [drm] radeon: 512M of GTT memory ready. [ 17.544061] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 17.544453] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 17.555887] [drm] Loading RV610 Microcode [ 17.910231] [drm] PCIE GART of 512M enabled (table at 0x0004). [ 17.910278] radeon :01:00.0: WB enabled [ 17.910281] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x1c00 and cpu addr 0x880115f00c00 [ 17.910283] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x1c0c and cpu addr 0x880115f00c0c [ 17.910289] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 17.910290] [drm] Driver supports precise vblank timestamp query. [ 17.910308] radeon :01:00.0: irq 51 for MSI/MSI-X [ 17.910318] radeon :01:00.0: radeon: using MSI. [ 17.910339] [drm] radeon: irq initialized. [ 17.941667] [drm] ring test on 0 succeeded in 1 usecs [ 17.941724] [drm] ring test on 3 succeeded in 1 usecs [ 17.942047] [drm] ib test on ring 0 succeeded in 0 usecs [ 17.942058] [drm] ib test on ring 3 succeeded in 0 usecs [ 17.942266] [drm] Radeon Display Connectors [ 17.942268] [drm] Connector 0: [ 17.942269] [drm] DIN-1 [ 17.942270] [drm] Encoders: [ 17.942271] [drm] TV1: INTERNAL_KLDSCP_DAC2 [ 17.942272] [drm] Connector 1: [ 17.942273] [drm] DVI-I-1 [ 17.942274] [drm] HPD2 [ 17.942276] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [ 17.942277] [drm] Encoders: [ 17.942278] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [ 17.942279] [drm] DFP1: INTERNAL_KLDSCP_TMDS1 [ 17.942280] [drm] Connector 2: [ 17.942281] [drm] DVI-I-2 [ 17.942282] [drm] HPD1 [ 17.942283] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [ 17.942284] [drm] Encoders: [ 17.942285] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 17.942286] [drm] DFP2: INTERNAL_LVTM1 [ 17.942294] [drm] Internal thermal controller with fan control [ 17.942325] [drm] radeon: power management initialized [ 18.013016] [drm] fb mappable at 0xD0142000 [ 18.013019] [drm] vram apper at 0xD000 [ 18.013020] [drm] size 7299072 [ 18.013021] [drm] fb depth is 24 [ 18.013022] [drm]pitch is 6912 [ 18.013081] fbcon: radeondrmfb (fb0) is primary device [ 18.215983] radeon :01:00.0: fb0: radeondrmfb frame buffer device [ 18.215984] radeon :01:00.0: registered panic notifier [ 18.215989] [drm] Initialized radeon 2.34.0 20080528 for :01:00.0 on minor 0 [ 1658.773964] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 202 [ 1658.775016] [drm:radeon_dvi_detect] *ERROR* DVI-I-2: probed a monitor but no|invalid EDID [ 1669.407596] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 165 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-radeon (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,gnomecompat,mousepoll,place,grid,regex,move,wall,vpswitch,obs,commands,snap,imgpng,animation,resize,session,unitymtgrabhandles,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 16 11:23:57 2013 DistUpgraded: 2013-10-15 14
[Desktop-packages] [Bug 1240145] Re: problems configuring facebook for sharing
** Changed in: gallery-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to friends in Ubuntu. https://bugs.launchpad.net/bugs/1240145 Title: problems configuring facebook for sharing Status in “friends” package in Ubuntu: Invalid Status in “gallery-app” package in Ubuntu: In Progress Bug description: using latest image 97 - open photo in gallery - press sharing button and then "configure facebook for sharing" - correctly brought to online accounts settings panel - configure facebook - after pressing "Log On" from facebook page you are automatically brought back to gallery (not sure this is desired, should bring you back to online accounts screen) - when in gallery, clicking the share button still shows "configure facebook for sharing" even though it has been configured - gallery does not recongnize facebook has been configured until you close and relaunch gallery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1240145/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240145] Re: problems configuring facebook for sharing
** Branch linked: lp:~amanzi-team/ubuntu-ui-extras/ubuntu-ui-extras- facebook-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to friends in Ubuntu. https://bugs.launchpad.net/bugs/1240145 Title: problems configuring facebook for sharing Status in “friends” package in Ubuntu: Invalid Status in “gallery-app” package in Ubuntu: In Progress Bug description: using latest image 97 - open photo in gallery - press sharing button and then "configure facebook for sharing" - correctly brought to online accounts settings panel - configure facebook - after pressing "Log On" from facebook page you are automatically brought back to gallery (not sure this is desired, should bring you back to online accounts screen) - when in gallery, clicking the share button still shows "configure facebook for sharing" even though it has been configured - gallery does not recongnize facebook has been configured until you close and relaunch gallery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1240145/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240432] [NEW] evince segmentation fault. invalid rectangle passed
Public bug reported: Ubuntu 13.10 evince 3.10.0-0ubuntu2 libcairo2 1.12.16-0ubuntu2 Steps to reproduce: Attempt to view this pdf in evince: http://www.mouser.com/ds/2/427/rwmilita-239699.pdf Results: evince shows the document first page for a second or two and then crashes. Console Output: (evince:2064): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Segmentation fault (core dumped) gdb output: *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f90c7fff700 (LWP 19298)] active_edges (polygon=0x7f90c7ffdd10, top=7401, left=0x7f90bc424170) at /build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c:1235 1235/build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c: No such file or directory. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1240432 Title: evince segmentation fault. invalid rectangle passed Status in “gnome-panel” package in Ubuntu: New Bug description: Ubuntu 13.10 evince 3.10.0-0ubuntu2 libcairo2 1.12.16-0ubuntu2 Steps to reproduce: Attempt to view this pdf in evince: http://www.mouser.com/ds/2/427/rwmilita-239699.pdf Results: evince shows the document first page for a second or two and then crashes. Console Output: (evince:2064): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Segmentation fault (core dumped) gdb output: *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f90c7fff700 (LWP 19298)] active_edges (polygon=0x7f90c7ffdd10, top=7401, left=0x7f90bc424170) at /build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c:1235 1235/build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c: No such file or directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1240432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1008548] Re: Unable to click the title bar, can't move windows
I have the same issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1008548 Title: Unable to click the title bar, can't move windows Status in “metacity” package in Ubuntu: Confirmed Bug description: Every now and then the title bar on certain windows becomes inaccessible, and clicking it clicks whatever is behind it. Other windows function normally. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Mon Jun 4 10:16:48 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1008548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
After reformatting and using the Ubuntu 13.04 Minimal CD, immediately running sudo sed -i 's/raring/saucy/g' /etc/apt/sources.list and reinstalling all of my stuff, I have sound in Ubuntu 13.10. Still, I'm not sure what caused me to lose sound when upgrading from Ubuntu 13.04 to Ubuntu 13.10. -- 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/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in The Linux Kernel: New Status in “alsa-driver” package in Ubuntu: Triaged Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX 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.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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/alsa-driver/+bug/1166529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240145] Re: problems configuring facebook for sharing
** Branch linked: lp:~amanzi-team/gallery-app/gallery-app-check-facebook -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to friends in Ubuntu. https://bugs.launchpad.net/bugs/1240145 Title: problems configuring facebook for sharing Status in “friends” package in Ubuntu: Invalid Status in “gallery-app” package in Ubuntu: In Progress Bug description: using latest image 97 - open photo in gallery - press sharing button and then "configure facebook for sharing" - correctly brought to online accounts settings panel - configure facebook - after pressing "Log On" from facebook page you are automatically brought back to gallery (not sure this is desired, should bring you back to online accounts screen) - when in gallery, clicking the share button still shows "configure facebook for sharing" even though it has been configured - gallery does not recongnize facebook has been configured until you close and relaunch gallery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1240145/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1230148] Re: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible()
This bug was fixed in the package network-manager-applet - 0.9.8.0-1ubuntu5 --- network-manager-applet (0.9.8.0-1ubuntu5) saucy; urgency=low * debian/patches/nm-applet-use-indicator.patch: - Fix crash when nm-applet quits (LP: #1230148) -- Robert AncellWed, 16 Oct 2013 16:35:33 +1300 ** Changed in: network-manager-applet (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1230148 Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() Status in “network-manager-applet” package in Ubuntu: Fix Released Bug description: After logging back in from a mir test session (installed unity-system- compositor, reboot, play with mir a bit, remove mir from lightdm startup, reboot). ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: network-manager-gnome 0.9.8.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Sun Sep 22 11:22:01 2013 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-23 (63 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.254 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.64 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet SegvAnalysis: Segfault happened at: 0x7f4e8813aa4c : cmp%rax,(%rdx) PC (0x7f4e8813aa4c) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: network-manager-applet StacktraceTop: gtk_status_icon_set_visible () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libappindicator3.so.1 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: nm-applet crashed with SIGSEGV in gtk_status_icon_set_visible() UpgradeStatus: Upgraded to saucy on 2013-07-27 (59 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo nmcli-dev: DEVICE TYPE STATE DBUS-PATH 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-applet/+bug/1230148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1231841] Re: lightdm crashed with SIGABRT in _g_log_abort()
This bug was fixed in the package lightdm - 1.8.2-0ubuntu1 --- lightdm (1.8.2-0ubuntu1) saucy; urgency=low * New upstream release: - Fix crash when starting with existing X servers. This was introduced in rev 1651 (lightdm 1.7.0). (LP: #1231841) -- Robert AncellWed, 16 Oct 2013 15:46:40 +1300 ** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Released -- 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/1231841 Title: lightdm crashed with SIGABRT in _g_log_abort() Status in Light Display Manager: Fix Committed Status in “lightdm” package in Ubuntu: Fix Released Bug description: Lightdm continue to crash on my two systems. Ati and Nvidia. Usually every 2 or 3 boot lightdm doesn't start. This is very very annoying please fix this issue. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Thu Sep 26 22:20:20 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2013-09-22 (4 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130905) MarkForUpload: True ProcCmdline: lightdm restart Signal: 6 SourcePackage: lightdm StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_filename_display_name () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: lightdm crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1231841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1155825] Re: [printers]: gnome-control-center crashed with SIGABRT in __libc_message()
This bug was fixed in the package gnome-control-center - 1:3.6.3-0ubuntu44 --- gnome-control-center (1:3.6.3-0ubuntu44) saucy; urgency=low * debian/patches/git_add_printer_crash.patch: - Fix crash when adding a printer (LP: #1155825) -- Robert AncellWed, 16 Oct 2013 15:51:53 +1300 ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1155825 Title: [printers]: gnome-control-center crashed with SIGABRT in __libc_message() Status in GNOME Control Center: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Bug description: just tried to add a HP LazerJet 5 printer which is already up & running on all my other Linux Distros ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu15 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic i686 ApportVersion: 2.9.1-0ubuntu1 Architecture: i386 Date: Fri Mar 15 18:28:10 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-03-15 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha i386 (20130313) MarkForUpload: True ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: [printers]: gnome-control-center crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1155825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240450] [NEW] package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build
Public bug reported: gustavod@xps:~$ uname -a Linux xps 3.0.0-32-generic #51~lucid1-Ubuntu SMP Fri Mar 22 17:34:23 UTC 2013 x86_64 GNU/Linux gustavod@xps:~$ lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 gustavod@xps:~$ apt-cache policy nvidia-current nvidia-current: Instalado: 195.36.24-0ubuntu1~10.04.3 Candidato: 195.36.24-0ubuntu1~10.04.3 Tabela de versão: *** 195.36.24-0ubuntu1~10.04.3 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/restricted Packages 100 /var/lib/dpkg/status 195.36.15-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/restricted Packages ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.24-0ubuntu1~10.04.3 ProcVersionSignature: Ubuntu 3.0.0-32.51~lucid1-generic 3.0.69 Uname: Linux 3.0.0-32-generic x86_64 Architecture: amd64 Date: Wed Oct 16 06:53:53 2013 DkmsStatus: vboxhost, 4.2.18, 2.6.32-52-generic, x86_64: installed vboxhost, 4.2.18, 3.0.0-32-generic, x86_64: installed nvidia-current, 195.36.24, 2.6.32-52-generic, x86_64: installed ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Dell Inc. XPS M1330 PackageVersion: 195.36.24-0ubuntu1~10.04.3 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-32-generic root=UUID=9402aea0-f9bc-4dc6-8825-7a297fc5adce ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] Arquivo ou diretório não encontrado system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 3.0.0-32-generic ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1240450 Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: gustavod@xps:~$ uname -a Linux xps 3.0.0-32-generic #51~lucid1-Ubuntu SMP Fri Mar 22 17:34:23 UTC 2013 x86_64 GNU/Linux gustavod@xps:~$ lsb_release -rd Description: Ubuntu 10.04.4 LTS Release: 10.04 gustavod@xps:~$ apt-cache policy nvidia-current nvidia-current: Instalado: 195.36.24-0ubuntu1~10.04.3 Candidato: 195.36.24-0ubuntu1~10.04.3 Tabela de versão: *** 195.36.24-0ubuntu1~10.04.3 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/restricted Packages 100 /var/lib/dpkg/status 195.36.15-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/restricted Packages ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.24-0ubuntu1~10.04.3 ProcVersionSignature: Ubuntu 3.0.0-32.51~lucid1-generic 3.0.69 Uname: Linux 3.0.0-32-generic x86_64 Architecture: amd64 Date: Wed Oct 16 06:53:53 2013 DkmsStatus: vboxhost, 4.2.18, 2.6.32-52-generic, x86_64: installed vboxhost, 4.2.18, 3.0.0-32-generic, x86_64: installed nvidia-current, 195.36.24, 2.6.32-52-generic, x86_64: installed ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Dell Inc. XPS M1330 PackageVersion: 195.36.24-0ubuntu1~10.04.3 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-32-generic root=UUID=9402aea0-f9bc-4dc6-8825-7a297fc5adce ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] Arquivo ou diretório não encontrado system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 3.0.0-32-generic To manage notifications about this bug go to:
[Desktop-packages] [Bug 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0
** Tags added: scopes-s -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to activity-log-manager in Ubuntu. https://bugs.launchpad.net/bugs/1197569 Title: Move from zeitgeist-1.0 to zeitgeist-2.0 Status in Bijiben: Fix Released Status in Cairo-Dock: Plug-ins: Fix Released Status in Diodon - GTK+ Clipboard Manager: Triaged Status in Scratch: Fix Committed Status in Totem Movie Player: Fix Released Status in Unity: Fix Released Status in Unity Applications Lens: In Progress Status in Unity Files Lens: Fix Committed Status in Unity Videos Lens: In Progress Status in Upstart Application Launcher: Triaged Status in “activity-log-manager” package in Ubuntu: Fix Released Status in “bijiben” package in Ubuntu: New Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Released Status in “diodon” package in Ubuntu: Fix Released Status in “folks” package in Ubuntu: New Status in “nautilus” package in Ubuntu: Confirmed Status in “synapse” package in Ubuntu: New Status in “totem” package in Ubuntu: New Status in “unity” package in Ubuntu: Fix Released Status in “unity-lens-applications” package in Ubuntu: In Progress Status in “unity-lens-files” package in Ubuntu: Fix Released Status in “unity-lens-video” package in Ubuntu: In Progress Status in “upstart-app-launch” package in Ubuntu: New Bug description: The older libzeitgeist (http://launchpad.net/libzeitgeist) served its days and will be deprecated soon. All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0) To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1197569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1088849] Re: Applications lens is blank on first use
Seems to be the case only in 12.04 with Unity2d (and not always). Works fine in Unity in 12.04 and 13.10. ** No longer affects: unity ** Also affects: unity-2d Importance: Undecided Status: New ** Changed in: unity-lens-applications Status: Confirmed => Invalid ** Changed in: unity-lens-applications (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-lens-applications in Ubuntu. Matching subscriptions: dp-unity-lens-music https://bugs.launchpad.net/bugs/1088849 Title: Applications lens is blank on first use Status in Unity 2D: New Status in Unity Applications Lens: Invalid Status in “unity-lens-applications” package in Ubuntu: Invalid Bug description: unity 6.10.0-0ubuntu2, Ubuntu 12.10 1. Switch to a guest session. 2. Open the Dash. 3. Click the Applications button. 4. Click any other lens button. 5. Click the Applications button again. What happens: 3. The Dash goes blank. 5. The Applications lens populates properly. What should happen: 3. The Applications lens populates properly. A similar thing happens with the Music lens, bug 1045770. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/1088849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 968974] Re: Some free applications looks like paid applications with price 0.00 and with buy button
** Tags added: scopes-s ** Changed in: unity-lens-applications Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/968974 Title: Some free applications looks like paid applications with price 0.00 and with buy button Status in One Hundred Paper Cuts: Triaged Status in Ubuntu Software Center: Confirmed Status in Unity Applications Lens: Confirmed Status in “software-center” package in Ubuntu: Triaged Status in “unity-lens-applications” package in Ubuntu: Triaged Bug description: Just watch an attachment screenshot. Pages of some free applications looks like as pages of paid applications, but with zero price. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: software-center 5.1.13.2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 Date: Fri Mar 30 11:19:48 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/968974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1237564] Re: Regression: some previous keyboard bindings & all newly created custom bindings fail if gnome-screensaver isn't installed
This bug was fixed in the package gnome-settings-daemon - 3.8.5-0ubuntu8 --- gnome-settings-daemon (3.8.5-0ubuntu8) saucy; urgency=low * debian/patches/fix_media_keys_on_unity.patch: Don't rely on org.gnome.ScreenSaver as this might not be available (it's only a recommends of ubuntu-desktop). Use the names owned by (critical components of) the DEs themselves instead. (LP: #1237564) -- Iain LaneWed, 16 Oct 2013 09:39:12 +0100 ** Changed in: gnome-settings-daemon (Ubuntu) Status: In Progress => 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/1237564 Title: Regression: some previous keyboard bindings & all newly created custom bindings fail if gnome-screensaver isn't installed Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Bug description: [ Description ] gnome-settings-daemon 3.8.5-0ubuntu7 used the presence of org.gnome.ScreenSaver on the session bus to decide whether to activate the media keys plugin (used for volume up/down, skipping tracks, brightness and so on). This package is only a Recommends of ubuntu-desktop. It's an undeclared dependency which isn't actually necessary. [ Proposed fix ] Check for org.gnome.Panel (for gnome-panel environments) and com.canonical.Unity (for Unity environments). Unity also provides org.gnome.Shell so check $DESKTOP_SESSION in that handler to only run in a real gnome-shell session. [ Test case ] Remove the gnome-screensaver package. In a gnome-panel based or a Unity session, launch gnome-settings-daemon. Make sure your media keys work with the update. [ Regression potential ] This changes activation of a plugin. There's a chance it could be wrong. If it doesn't work, make sure the plugin is enabled: $ gsettings get org.gnome.settings-daemon.plugins.media-keys active and then run $ gnome-settings-daemon --debug --replace | tee /tmp/g-s-d.log wait 5 seconds, try pressing some media keys, then attach /tmp/g-s-d.log [ Original report ] With the latest g-s-d any custom key-bindings fail as do some 'default* ones (system Test cases - remove gnome-screensaver open keyboard panel > shortcuts> system change Log out to a new binding log out/in thru indicator-session Try the new binding, nothing happens open keyboard panel > shortcuts> custom create a new binding for some command log out/in use binding, nothing happens ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 9 14:03:35 2013 InstallationDate: Installed on 2013-10-03 (6 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/ubuntu/+source/gnome-settings-daemon/+bug/1237564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196051] Re: smart-scopes: Software center results do not show up in the home-scope
This is by design: apps in Home should only include installed apps. "More suggestions" in Applications scope is the only place in the dash where additional apps available from S-C should be listed. While it would be relatively simple to display suggested apps in Home, it would mean they would be mixed together with recently used applications (since in Home results coming from a scope are merged and collapse into single category). ** Changed in: unity-scope-home Status: New => Won't Fix ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1196051 Title: smart-scopes: Software center results do not show up in the home-scope Status in Unity Home Scope: Won't Fix Status in “unity” package in Ubuntu: Invalid Bug description: No useful (or smart) search results returned for apps not currently installed, i.e. Steam, Gimp, etc. to the Home-Scope. However, the apps-scope already has this implemented. Fix needed: Add useful software center results also to the home-scope as per the goal to make the dash searches smart. --- original report: clean install of saucy, searched for chromium, banshee, etc. on either of these a Info icon for wikipedia is shown or chromium bookmarks was shown but not the application itself. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scope-home/+bug/1196051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240466] [NEW] package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build
Public bug reported: gustavod@vostro:~$ uname -a Linux vostro 2.6.32-52-generic #114-Ubuntu SMP Wed Sep 11 18:50:27 UTC 2013 x86_64 GNU/Linux gustavod@vostro:~$ lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 gustavod@vostro:~$ apt-cache policy nvidia-current nvidia-current: Instalado: 195.36.24-0ubuntu1~10.04.3 Candidato: 195.36.24-0ubuntu1~10.04.3 Tabela de versão: *** 195.36.24-0ubuntu1~10.04.3 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/restricted Packages 100 /var/lib/dpkg/status 195.36.15-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/restricted Packages ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.24-0ubuntu1~10.04.3 ProcVersionSignature: Ubuntu 2.6.32-52.114-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-52-generic x86_64 Architecture: amd64 Date: Wed Oct 16 07:44:34 2013 DkmsStatus: nvidia-current, 195.36.24, 2.6.32-52-generic, x86_64: installed ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Dell Inc. Vostro 270s PackageVersion: 195.36.24-0ubuntu1~10.04.3 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-52-generic root=UUID=ba8290ab-9997-41a9-b160-145664499256 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 11/22/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0478VN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/22/2012:svnDellInc.:pnVostro270s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 270s dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] Arquivo ou diretório não encontrado system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-52-generic ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1240466 Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: gustavod@vostro:~$ uname -a Linux vostro 2.6.32-52-generic #114-Ubuntu SMP Wed Sep 11 18:50:27 UTC 2013 x86_64 GNU/Linux gustavod@vostro:~$ lsb_release -rd Description: Ubuntu 10.04.4 LTS Release: 10.04 gustavod@vostro:~$ apt-cache policy nvidia-current nvidia-current: Instalado: 195.36.24-0ubuntu1~10.04.3 Candidato: 195.36.24-0ubuntu1~10.04.3 Tabela de versão: *** 195.36.24-0ubuntu1~10.04.3 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/restricted Packages 100 /var/lib/dpkg/status 195.36.15-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ lucid/restricted Packages ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.24-0ubuntu1~10.04.3 ProcVersionSignature: Ubuntu 2.6.32-52.114-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-52-generic x86_64 Architecture: amd64 Date: Wed Oct 16 07:44:34 2013 DkmsStatus: nvidia-current, 195.36.24, 2.6.32-52-generic, x86_64: installed ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MachineType: Dell Inc. Vostro 270s PackageVersion: 195.36.24-0ubuntu1~10.04.3 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-52-generic root=UUID=ba8290ab-9997-41a9-b160-145664499256 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.24-0ubuntu1~10.04.3 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 11/22/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0478VN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/22/2012:svnDellInc.:pnVostro270s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 270s dmi.sys.vendor: Dell Inc. glxinfo: Error: [Errno 2] Arquivo ou diretório não encontrado system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-52-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-driver
[Desktop-packages] [Bug 1192081] Re: Previews for applications are really slow to display anything
** Tags added: scopes-s -- 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/1192081 Title: Previews for applications are really slow to display anything Status in Ubuntu Software Center: Confirmed Status in Unity Applications Lens: Triaged Status in “software-center” package in Ubuntu: Triaged Status in “unity-lens-applications” package in Ubuntu: Triaged Bug description: I'm seeing rightly on forums and generally the Internet that 100scopes previews are slow, combined with the fact that we now have the left click showing the preview by default frustrate a lot of users. On my beefy machine (i7, 8G of rams), the preview for an application takes 3/4s to show, you can't do anything meanwhile as there is no button to launch the application (because you didn't double click, just left click and thought "argh, I should have double click"). Because of this, we are making the 1st landing of 100 scopes experience bad and we should fix it (at least, in that applicatoin lens) by either preloading the software-center-dbus (/usr/share /software-center/software-center-dbus) daemon (we can't have it always running as it's taking over 100MB of memory) when hovering an app lens result, or when it's the first result (so can be directly triggered by pressing [Enter]) To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1192081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240467] [NEW] Incorrect volume level and audio routing after call received during music playback with headphones
Public bug reported: mako 20131015.2 TEST CASE: 1. Insert headphones into phone 2. Start music playback through the headphones 3. Receive an incoming call on the device and answer the call 4. End the call EXPECTED RESULT: Music playback should pause when the call is received When the call has ended, playback should resume through the headphones at the previous volume level ACTUAL RESULT: When the phone receives the call, the music playback changes to loud speaker After the call has ended, the music volume level is very loud and plays through the loud speaker rather than the headphones. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 Uname: Linux 3.4.0-3-mako armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Wed Oct 16 10:52:52 2013 InstallationDate: Installed on 2013-10-15 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131015.2) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pulseaudio (Ubuntu) Importance: High Status: New ** Affects: pulseaudio (Ubuntu Saucy) Importance: High Status: New ** Tags: apport-bug armhf avengers qa-touch rls-s-incoming saucy ** Also affects: pulseaudio (Ubuntu Saucy) Importance: High Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1240467 Title: Incorrect volume level and audio routing after call received during music playback with headphones Status in “pulseaudio” package in Ubuntu: New Status in “pulseaudio” source package in Saucy: New Bug description: mako 20131015.2 TEST CASE: 1. Insert headphones into phone 2. Start music playback through the headphones 3. Receive an incoming call on the device and answer the call 4. End the call EXPECTED RESULT: Music playback should pause when the call is received When the call has ended, playback should resume through the headphones at the previous volume level ACTUAL RESULT: When the phone receives the call, the music playback changes to loud speaker After the call has ended, the music volume level is very loud and plays through the loud speaker rather than the headphones. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 Uname: Linux 3.4.0-3-mako armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Wed Oct 16 10:52:52 2013 InstallationDate: Installed on 2013-10-15 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131015.2) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1240467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852710] Re: apps available to download are randomly chosen
This works fine from 13.04 (probably also in 12.10 but I cannot verify this at the moment), we display top apps (as reported vy Software Center) if the query is empty, otherwise only apps matching the query and selected app categories. Please re-open the bug if you still see any problem with it. ** Changed in: unity-lens-applications Status: Confirmed => Invalid ** Changed in: unity-lens-applications (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-lens-applications in Ubuntu. Matching subscriptions: dp-unity-lens-music https://bugs.launchpad.net/bugs/852710 Title: apps available to download are randomly chosen Status in Unity Applications Lens: Invalid Status in “unity-lens-applications” package in Ubuntu: Invalid Bug description: on unity 2d / 11.10 beta up to date as of 17 September 2011, the "more apps" shown at the bottom of any category seems fully random and unrelated to the category, and also appears to change each time the dash home is re-invoked. For example "dash home" > "more apps" > "accessibility" this time around shows, under "more apps availabe for download": "magicicada" "mines" "mpong-gl" "camoso" (and two more not shown). Seems those are all games? Not accessibility? I could understand a different set of alternatives for download shown on each invocation, but showing apps unrelated to the category seems really weird. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/852710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Is this still a problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) Status in Light Display Manager: New Status in NVIDIA Drivers Ubuntu: New Status in “lightdm” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Triaged Status in “nvidia-graphics-drivers” source package in Precise: Confirmed Bug description: Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX 485M, GTX 560M or GTX 580M. Appears to be a race condition. LightDM attempts to start before /dev/nvidiactrl is created. As a workaround add "sleep 1 && service lightdm start" to /etc/rc.local to start the service. ### This workaround is insufficient. Some users have reported that their systems do not start after initial user setup. Deleting the contents of /var/run/dbus/* resolves the issue in these cases. ### ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell] CompositorRunning: compiz Date: Thu Oct 13 11:05:18 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5102] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: System76, Inc. Serval Professional ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 01/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/873495/+subscriptions -- Maili
[Desktop-packages] [Bug 1233319] Re: Faily autopilot tests blocking daily_release.
fails are down, there have been a few releases into distro since this vague bug was filed. Since there's no single problem, there's no single fix to associate here. Closing manually. ** Changed in: unity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1233319 Title: Faily autopilot tests blocking daily_release. Status in “unity” package in Ubuntu: Fix Released Bug description: Today I'm seeing 43 failing autopilot tests for unity. Here is the overview: http://10.97.0.1:8080/job/autopilot-saucy- daily_release/2239/#showFailuresLink This is blocking the unity stack (including important updates from libunity and unity-scope-home) from landing in distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1233319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236340] Re: new upstream release 9.1.7
radeon: works, one test that failed to link is now crashing. But it printed � before, so big chance it was just showing garbage and under the right conditions it would already crash. -- 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/1236340 Title: new upstream release 9.1.7 Status in “mesa” package in Ubuntu: Invalid Status in “mesa” source package in Raring: Fix Committed Bug description: [Impact] Fixes following upstream bugs: (9.1.5) 58384 - [i965 Bisected]Oglc max_values(advanced.fragmentProgram.GL_MAX_PROGRAM_ENV_PARAMETERS_ARB) segfault 62647 - Wrong rendering of Dota 2 on Wine (apitrace attached) - Intel IVB HD4000 63674 - [IVB]frozen at the first frame when run Unigine-heaven 4.0 65910 - Killing weston-launch causes segv in desktop-shell (9.1.6) 47824 - osmesa using --enable-shared-glapi depends on libgl 62362 - Crash when using Wayland EGL platform 63435 - [Regression since 9.0] Flickering in EGL OpenGL full-screen window with swap interval 1 64087 - Webgl conformance shader-with-non-reserved-words crash when mesa is compiled without --enable-debug 64330 - WebGL snake demo crash in loop_analysis.cpp:506: bool is_loop_terminator(ir_if*): assertion „inst != __null“ failed. 65236 - [i965] Rendering artifacts in VDrift/GL2 66558 - RS690: 3D artifacts when playing SuperTuxKart 66847 - compilation broken with llvm 3.3 66850 - glGenerateMipmap crashes when using GL_TEXTURE_2D_ARRAY with compressed internal format 66921 - [r300g] Heroes of Newerth: HiZ related corruption 67283 - VDPAU doesn't work on hybrid laptop through DRI_PRIME (9.1.7) 55503 - Constant vertex attributes broken 61635 - glVertexAttribPointer(id, GL_UNSIGNED_BYTE, GL_FALSE,...) does not work 65958 - GPU Lockup on Trinity 7500G 66292 - [SNB/IVB/HSW Bisected]Ogles3conform GL3Tests_depth24_depth24_basic.test fail 67548 - glGetAttribLocation seems to be broken 68195 - piglit tests vs-struct-pad and fs-struct-pad both fail 68250 - Automatic mipmap generation with texture compression produces borders that fade to black 69525 - [GM45, bisected] Piglit tex-shadow2drect fails [Test case] * A full piglit run will be done on i915, nouveau and ati. Unity dash will be explicitly tested on intel cards for any slowdowns. [Regression potential] * Saucy had mesa up to 9.1.6 before switching to the 9.2 branch. There were no specific regressions from the 9.1.4 version in raring-updates. But there's always the possibility for regressions like gpu lockups and rendering errors. Those should be watched. [Other] Mesa has a MRE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1236340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236340] Re: new upstream release 9.1.7
nouveau: 3 tests failing. retesting them on 9.1.4 shows that they're flaky before too, so not a real regression. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1236340 Title: new upstream release 9.1.7 Status in “mesa” package in Ubuntu: Invalid Status in “mesa” source package in Raring: Fix Committed Bug description: [Impact] Fixes following upstream bugs: (9.1.5) 58384 - [i965 Bisected]Oglc max_values(advanced.fragmentProgram.GL_MAX_PROGRAM_ENV_PARAMETERS_ARB) segfault 62647 - Wrong rendering of Dota 2 on Wine (apitrace attached) - Intel IVB HD4000 63674 - [IVB]frozen at the first frame when run Unigine-heaven 4.0 65910 - Killing weston-launch causes segv in desktop-shell (9.1.6) 47824 - osmesa using --enable-shared-glapi depends on libgl 62362 - Crash when using Wayland EGL platform 63435 - [Regression since 9.0] Flickering in EGL OpenGL full-screen window with swap interval 1 64087 - Webgl conformance shader-with-non-reserved-words crash when mesa is compiled without --enable-debug 64330 - WebGL snake demo crash in loop_analysis.cpp:506: bool is_loop_terminator(ir_if*): assertion „inst != __null“ failed. 65236 - [i965] Rendering artifacts in VDrift/GL2 66558 - RS690: 3D artifacts when playing SuperTuxKart 66847 - compilation broken with llvm 3.3 66850 - glGenerateMipmap crashes when using GL_TEXTURE_2D_ARRAY with compressed internal format 66921 - [r300g] Heroes of Newerth: HiZ related corruption 67283 - VDPAU doesn't work on hybrid laptop through DRI_PRIME (9.1.7) 55503 - Constant vertex attributes broken 61635 - glVertexAttribPointer(id, GL_UNSIGNED_BYTE, GL_FALSE,...) does not work 65958 - GPU Lockup on Trinity 7500G 66292 - [SNB/IVB/HSW Bisected]Ogles3conform GL3Tests_depth24_depth24_basic.test fail 67548 - glGetAttribLocation seems to be broken 68195 - piglit tests vs-struct-pad and fs-struct-pad both fail 68250 - Automatic mipmap generation with texture compression produces borders that fade to black 69525 - [GM45, bisected] Piglit tex-shadow2drect fails [Test case] * A full piglit run will be done on i915, nouveau and ati. Unity dash will be explicitly tested on intel cards for any slowdowns. [Regression potential] * Saucy had mesa up to 9.1.6 before switching to the 9.2 branch. There were no specific regressions from the 9.1.4 version in raring-updates. But there's always the possibility for regressions like gpu lockups and rendering errors. Those should be watched. [Other] Mesa has a MRE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1236340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
@Hotteterre Upstream bug report https://bugzilla.gnome.org/show_bug.cgi?id=706254 hints the assumption that this bug is not depended on any particular gvfs protocol. So I would assume at the moment that your bug is another manisfestation of the bug reported here, thus it is not necessary to create a separate report. ** Bug watch added: GNOME Bug Tracker #706254 https://bugzilla.gnome.org/show_bug.cgi?id=706254 -- 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/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: New Status in “gvfs” package in Ubuntu: Confirmed Status in “gvfs” package in Debian: New Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+subscriptions -- Mailing list: https://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 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Seems to be not an issue with wither 13.04 or 13.10. Thanks to those who fixed it. frank On 10/16/2013 04:30 AM, Alberto Milone wrote: > Is this still a problem? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) Status in Light Display Manager: New Status in NVIDIA Drivers Ubuntu: New Status in “lightdm” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Triaged Status in “nvidia-graphics-drivers” source package in Precise: Confirmed Bug description: Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX 485M, GTX 560M or GTX 580M. Appears to be a race condition. LightDM attempts to start before /dev/nvidiactrl is created. As a workaround add "sleep 1 && service lightdm start" to /etc/rc.local to start the service. ### This workaround is insufficient. Some users have reported that their systems do not start after initial user setup. Deleting the contents of /var/run/dbus/* resolves the issue in these cases. ### ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell] CompositorRunning: compiz Date: Thu Oct 13 11:05:18 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5102] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: System76, Inc. Serval Professional ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 01/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.1
[Desktop-packages] [Bug 1180881] Re: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch
** Also affects: hwe-next Importance: Undecided Status: New ** Changed in: hwe-next Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1180881 Title: Touchscreen only works after suspend/resume on Lenovo ideapad P400 Touch Status in HWE Next Project: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Fix Committed Bug description: Touchscreen is unresponsive on fresh 13.04 Ubuntu installation. All other devices work. Touchscreen shows as working and 'states' are correct for any xinput --list off of a cold boot. However, if I (at any point) "Suspend" the system, then awaken it, the Touchscreen immediately functions properly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1180881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950352] Re: Online Accounts UI Missing
This is happening to me on 12.04. It was installed as 12.04, and I know Online Accounts was visible, so it's changed during a package update some time in the last few months. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/950352 Title: Online Accounts UI Missing Status in “empathy” package in Ubuntu: Confirmed Status in “gnome-online-accounts” package in Ubuntu: Confirmed Bug description: Recently upgraded from 11.10 to 12.04B1. I have no "Online Account..." option in the UI. Previously it was an option in the User Indicator. Though I was unable to find it in Settings or Searching Unity, I was able to access it through "Empathy" using the "Edit Connection Parameters..." for my Google chat account that was previously setup via GOA. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-online-accounts 3.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 15:48:23 2012 ProcEnviron: LANGUAGE=en TERM=xterm LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to precise on 2012-03-03 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/950352/+subscriptions -- Mailing list: https://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 873495] Re: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue)
Le 16/10/2013 13:30, Alberto Milone a écrit : > Is this still a problem? > not anymore on my side thanks for the fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/873495 Title: LightDM fails to start after nvidia-current or nvidia-current-updates are installed (upstart job issue) Status in Light Display Manager: New Status in NVIDIA Drivers Ubuntu: New Status in “lightdm” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Triaged Status in “nvidia-graphics-drivers” source package in Precise: Confirmed Bug description: Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX 485M, GTX 560M or GTX 580M. Appears to be a race condition. LightDM attempts to start before /dev/nvidiactrl is created. As a workaround add "sleep 1 && service lightdm start" to /etc/rc.local to start the service. ### This workaround is insufficient. Some users have reported that their systems do not start after initial user setup. Deleting the contents of /var/run/dbus/* resolves the issue in these cases. ### ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,snap,animation,resize,place,vpswitch,mousepoll,workarounds,gnomecompat,compiztoolbox,move,grid,imgpng,wall,fade,expo,session,unitymtgrabhandles,ezoom,scale,unityshell] CompositorRunning: compiz Date: Thu Oct 13 11:05:18 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: nvidia-current, 280.13, 3.0.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: nVidia Corporation Device [10de:0e31] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5102] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: System76, Inc. Serval Professional ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=79434c5f-d3ca-4224-98f2-06e7b36fbe32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 01/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications a
[Desktop-packages] [Bug 1222248] Re: regression: scroll areas on touchpad do not work any more
Also on Dell Latitude E5400, Edge scrolling stopped working after upgrade 13.04 to 13.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/148 Title: regression: scroll areas on touchpad do not work any more Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: After update to 13.10 scroll areas on T500 touchpad stopped working. There is no option to turn it backon. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu33 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sat Sep 7 22:38:14 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-09-05 (1 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240432] Re: evince segmentation fault. invalid rectangle passed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-panel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1240432 Title: evince segmentation fault. invalid rectangle passed Status in “evince” package in Ubuntu: Confirmed Bug description: Ubuntu 13.10 evince 3.10.0-0ubuntu2 libcairo2 1.12.16-0ubuntu2 Steps to reproduce: Attempt to view this pdf in evince: http://www.mouser.com/ds/2/427/rwmilita-239699.pdf Results: evince shows the document first page for a second or two and then crashes. Console Output: (evince:2064): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Segmentation fault (core dumped) gdb output: *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f90c7fff700 (LWP 19298)] active_edges (polygon=0x7f90c7ffdd10, top=7401, left=0x7f90bc424170) at /build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c:1235 1235/build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c: No such file or directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1240432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1237495] Re: [xmir] Xorg crashed with SIGABRT in __GI_raise()
Not enough information to diagnose the incomplete stacktrace, but the logs have plenty of issues with xmir. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- 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/1237495 Title: [xmir] Xorg crashed with SIGABRT in __GI_raise() Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: Tried 3.12.0-rc4 to fix resume and xorg failures and again got apport crash of xorg ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.14.3-3ubuntu1 Uname: Linux 3.12.0-031200rc4-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Wed Oct 9 10:23:04 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2adc] InstallationDate: Installed on 2013-07-10 (90 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130709) MachineType: Hewlett-Packard 520-1138cb MarkForUpload: True ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -mir 0 -mirSocket /tmp/mir_socket -nolisten tcp ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.12.0-031200rc4-generic root=UUID=ee63e052-abe5-4316-8499-10528ed15dd7 ro rootflags=subvol=@ crashkernel=384M-2G:64M,2G-:128M vt.handoff=7 Signal: 6 SourcePackage: xorg-server Stacktrace: #0 0x7f9167d11f77 in __GI_raise (sig=6, sig@entry=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 resultvar = 0 pid = 1142 selftid = 1142 Cannot access memory at address 0x7fff78c7c458 StacktraceTop: __GI_raise (sig=6, sig@entry=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/23/2012 dmi.bios.vendor: AMI dmi.bios.version: 7.09 dmi.board.asset.tag: 3CR22302J0 dmi.board.name: 2ADC dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.05 dmi.chassis.asset.tag: 3CR22302J0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.09:bd11/23/2012:svnHewlett-Packard:pn520-1138cb:pvr1.00:rvnPEGATRONCORPORATION:rn2ADC:rvr1.05:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 520-1138cb dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 9 10:31:41 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-0 DP-1DP-2 HDMI-1 HDMI-2 VGA-0 xserver.version: 2:1.14.3-3ubuntu1 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1237495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240432] Re: evince segmentation fault. invalid rectangle passed
** Tags added: amd64 gnome3 saucy ** Package changed: gnome-panel (Ubuntu) => evince (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1240432 Title: evince segmentation fault. invalid rectangle passed Status in “evince” package in Ubuntu: Confirmed Bug description: Ubuntu 13.10 evince 3.10.0-0ubuntu2 libcairo2 1.12.16-0ubuntu2 Steps to reproduce: Attempt to view this pdf in evince: http://www.mouser.com/ds/2/427/rwmilita-239699.pdf Results: evince shows the document first page for a second or two and then crashes. Console Output: (evince:2064): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Segmentation fault (core dumped) gdb output: *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f90c7fff700 (LWP 19298)] active_edges (polygon=0x7f90c7ffdd10, top=7401, left=0x7f90bc424170) at /build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c:1235 1235/build/buildd/cairo-1.12.16/src/cairo-polygon-intersect.c: No such file or directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1240432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240467] Re: Incorrect volume level and audio routing after call received during music playback with headphones
** Changed in: pulseaudio (Ubuntu Saucy) Status: New => Confirmed ** Changed in: pulseaudio (Ubuntu Saucy) Assignee: (unassigned) => David Henningsson (diwic) -- 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/1240467 Title: Incorrect volume level and audio routing after call received during music playback with headphones Status in “pulseaudio” package in Ubuntu: Confirmed Status in “pulseaudio” source package in Saucy: Confirmed Bug description: mako 20131015.2 TEST CASE: 1. Insert headphones into phone 2. Start music playback through the headphones 3. Receive an incoming call on the device and answer the call 4. End the call EXPECTED RESULT: Music playback should pause when the call is received When the call has ended, playback should resume through the headphones at the previous volume level ACTUAL RESULT: When the phone receives the call, the music playback changes to loud speaker After the call has ended, the music volume level is very loud and plays through the loud speaker rather than the headphones. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 Uname: Linux 3.4.0-3-mako armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.12.5-0ubuntu2 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' Date: Wed Oct 16 10:52:52 2013 InstallationDate: Installed on 2013-10-15 (0 days ago) InstallationMedia: Ubuntu 13.10 - armhf (20131015.2) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1240467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 354672] Re: package texlive-base 2007.dfsg.1-5 failed to install/upgrade: el subproceso post-installation script devolvió el código de salida de error 1
*** This bug is a duplicate of bug 312740 *** https://bugs.launchpad.net/bugs/312740 Hi there! I had the same problem with installing the package - it's all about an old error message that will be put out about "an over 5 year old latex.." because of this message the build will fail. To remove this message you can follow these instructions: http://my.opera.com/Michael-Dodl/blog/2011/06/24/latex-disabling-the-5 -year-time-bomb Hopefully it helps! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/354672 Title: package texlive-base 2007.dfsg.1-5 failed to install/upgrade: el subproceso post-installation script devolvió el código de salida de error 1 Status in “texlive-base” package in Ubuntu: New Bug description: Binary package hint: texlive-base it fails to install, Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Se instalaron de forma automática los siguientes paquetes y ya no son necesarios. wine-gecko libsdl-gfx1.2-4 mp3splt python-dev openoffice.org-l10n-common libeel2-data gs-common id3 evolution-documentation-es python-nautilus ufraw mp3info python2.6-dev wine openoffice.org-help-es mpgtx libeel2-2 winbind python-eyed3 pdftk openoffice.org-l10n-es Utilice «apt-get autoremove» para eliminarlos. Se instalarán los siguientes paquetes extras: texlive-extra-utils texlive-fonts-recommended texlive-generic-recommended texlive-latex-base texlive-latex-recommended texlive-pstricks tipa Paquetes sugeridos: texlive-doc-en dvi2tty dvidvi Se instalarán los siguientes paquetes NUEVOS: latex-beamer latex-xcolor lilypond lilypond-data pdfjam pgf prosper tetex-bin texlive texlive-base texlive-extra-utils texlive-fonts-recommended texlive-generic-recommended texlive-latex-base texlive-latex-recommended texlive-pstricks tipa 0 actualizados, 17 se instalarán, 0 para eliminar y 0 no actualizados. Se necesita descargar 24,5MB/31,3MB de archivos. Se utilizarán 99,2MB de espacio de disco adicional después de esta operación. ¿Desea continuar [S/n]? s Des:1 http://co.archive.ubuntu.com jaunty/main texlive-fonts-recommended 2007.dfsg.1-5 [7210kB] Des:2 http://co.archive.ubuntu.com jaunty/main texlive-latex-base 2007.dfsg.1-5 [1231kB] Des:3 http://co.archive.ubuntu.com jaunty/main texlive-latex-recommended 2007.dfsg.1-5 [1744kB] Des:4 http://co.archive.ubuntu.com jaunty/main tetex-bin 2007.dfsg.1-5 [25,8kB] Des:5 http://co.archive.ubuntu.com jaunty/universe lilypond-data 2.12.1-0ubuntu1 [2689kB] Des:6 http://co.archive.ubuntu.com jaunty/main latex-xcolor 2.11-1 [609kB] Des:7 http://co.archive.ubuntu.com jaunty/main pgf 2.00-1 [2897kB] Des:8 http://co.archive.ubuntu.com jaunty/main latex-beamer 3.07-1.1ubuntu1 [2192kB] Des:9 http://co.archive.ubuntu.com jaunty/universe lilypond 2.12.1-0ubuntu1 [1478kB] Des:10 http://co.archive.ubuntu.com jaunty/universe pdfjam 1.20-2ubuntu1 [18,2kB] Des:11 http://co.archive.ubuntu.com jaunty/main texlive-generic-recommended 2007.dfsg.1-5 [454kB]
[Desktop-packages] [Bug 1232947] Re: scp-dbus-service.py crashed with ValueError in decorator(): Corrupt type signature
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1232947 Title: scp-dbus-service.py crashed with ValueError in decorator(): Corrupt type signature Status in “system-config-printer” package in Ubuntu: Confirmed Bug description: Crash. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: system-config-printer-common 1.4.2+20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CupsErrorLog: E [29/Sep/2013:21:04:48 -0300] [Job 20] Unable to queue job for destination "Stylus-CX5600". Date: Sun Sep 29 21:04:51 2013 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py InstallationDate: Installed on 2013-07-31 (60 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724) InterpreterPath: /usr/bin/python2.7 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C MarkForUpload: True PackageArchitecture: all Papersize: letter ProcCmdline: /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-8-generic root=UUID=0c67119c-ddae-476a-b510-142ec598f691 ro rootflags=subvol=@ quiet splash vt.handoff=7 PythonArgs: ['/usr/share/system-config-printer/scp-dbus-service.py'] SourcePackage: system-config-printer Title: scp-dbus-service.py crashed with ValueError in decorator(): Corrupt type signature UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1232947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232947] Re: scp-dbus-service.py crashed with ValueError in decorator(): Corrupt type signature
This bug makes it impossible to configure 'any' USB printer I have running Ubuntu Gnome 13.10. ** Tags added: gnome3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1232947 Title: scp-dbus-service.py crashed with ValueError in decorator(): Corrupt type signature Status in “system-config-printer” package in Ubuntu: Confirmed Bug description: Crash. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: system-config-printer-common 1.4.2+20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CupsErrorLog: E [29/Sep/2013:21:04:48 -0300] [Job 20] Unable to queue job for destination "Stylus-CX5600". Date: Sun Sep 29 21:04:51 2013 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py InstallationDate: Installed on 2013-07-31 (60 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724) InterpreterPath: /usr/bin/python2.7 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C MarkForUpload: True PackageArchitecture: all Papersize: letter ProcCmdline: /usr/bin/python /usr/share/system-config-printer/scp-dbus-service.py ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-8-generic root=UUID=0c67119c-ddae-476a-b510-142ec598f691 ro rootflags=subvol=@ quiet splash vt.handoff=7 PythonArgs: ['/usr/share/system-config-printer/scp-dbus-service.py'] SourcePackage: system-config-printer Title: scp-dbus-service.py crashed with ValueError in decorator(): Corrupt type signature UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1232947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 312740] Re: package texlive-base 2007.dfsg.1-2 failed to install/upgrade: exit status 1 - fmtutil-sys failed
Hi there! I had the same problem with installing the package - it's all about an old error message that will be put out about "an over 5 year old latex.." because of this message the build will fail. To remove this message you can follow these instructions: http://my.opera.com/Michael-Dodl/blog/2011/06/24/latex-disabling-the-5 -year-time-bomb Hopefully it helps! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/312740 Title: package texlive-base 2007.dfsg.1-2 failed to install/upgrade: exit status 1 - fmtutil-sys failed Status in “texlive-base” package in Ubuntu: Confirmed Bug description: Binary package hint: texlive-base Achitechture Intrepid AMD64 KDE 4.2 beta 2. Error mesg included " Please fix manually (try dpkg --configure -a and/or apt-get -f install) in terminal... tried both to no avail. Didn't know if I should do new bug report or subscribe to another as Architechture different. Sorry it I've done the wrong thing. Timothy Liddy ProblemType: Package Architecture: amd64 DistroRelease: Ubuntu 8.10 ErrorMessage: subprocess post-installation script returned error exit status 1 Package: texlive-base 2007.dfsg.1-2 PackageArchitecture: all SourcePackage: texlive-base Title: package texlive-base 2007.dfsg.1-2 failed to install/upgrade: subprocess post-installation script returned error exit status 1 Uname: Linux 2.6.27-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/312740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed
update the default behaviour to do-nothing. ** Patch added: "proposed patch for precise" https://bugs.launchpad.net/gnome-settings-daemon/+bug/1065979/+attachment/3879281/+files/follow-lid.debdiff -- 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/1065979 Title: external/internal monitors mirrored on boot when laptop lid is closed Status in Gnome Settings Daemon: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” source package in Oneiric: Won't Fix Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “gnome-settings-daemon” source package in Quantal: Won't Fix Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Bug description: [Impact] * Booting laptop in docking station with lid closed results in low resolution (1024x768/aka clone mode) on external monitor * Low resolution desktop (1024x768) when user logs in, must be manually set to optimal resolution for external montior * non-technical users would find the default behaviour not the desired behaviour. [Test Case] Steps to Reproduce: 1. Connect an external monitor to laptop. 2. Boot system with lid closed with a clean new user 3. Login screen is shown at 1024x768 ( the highest common resolution supported by both the displays) The laptop display ( say 1366x768) should have a lower resolution than the connected external monitor ( say 1920x1080 ) . [Regression Potential] * I dont see any regression potential here, as this does not change any default behaviour. * User must manually activate this "new" behaviour . [Other Info] * test packages have been posted to - http://people.canonical.com/~ritesh/work/gsd/ * Update to this, and update default to "follow-lid" $ gsettings set org.gnome.settings-daemon.plugins.xrandr \ default-monitors-setup "follow-lid" * test as usual - If I put my X220 in a dock, and plug in an external monitor. Then I close the lid and turn on the computer, the computer will boot up with both the internal laptop screen and external monitor on and mirror. Because I can't see the laptop screen, I would expect the external monitor to be only on at its maximum resolution. I've actually tried this without the dock by plugging in an external monitor to my laptop and shutting the lid during boot quickly, the same problem persists. This problem is exhibited on Precise/Oneiric as well as Quantal. In particular this specification mentions this behavior: https://wiki.ubuntu.com/X/Blueprints/MultiMonitor In this user story: """Alan goes to the office, puts his laptop with the lid closed into a docking station and boots it up. The external display should be run at its native resolution. Later that day he needs to see a customer. He suspends the laptop and takes it out of the docking station. At the customer he wakes up the laptop and the internal screen is used at its native resolution. Finishing his visit the laptop is suspended, brought back to the office. There it is placed in the docking station, woken up and the external display should run again at its native resolution.""" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1065979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224621] Re: Removing libunity9 also removes nautilus and other packages
Nautilus and other packages are patched to support integration with Unity launcher, that's why they link with libunity. ** Changed in: libunity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1224621 Title: Removing libunity9 also removes nautilus and other packages Status in “libunity” package in Ubuntu: Invalid Bug description: $ apt-get -s remove libunity9 The following packages will be REMOVED: brasero brasero-cdrkit deja-dup deja-dup-backend-gvfs deja-dup-backend-ubuntuone empathy indicator-appmenu indicator-sound libbrasero-media3-1 libunity9 mcp-account-manager-uoa nautilus nautilus-sendto nautilus-sendto-empathy nautilus-share rhythmbox-plugin-cdrecorder shotwell telepathy-indicator xchat-indicator ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libunity9 6.90.2daily13.04.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 Date: Thu Sep 12 20:05:10 2013 InstallationDate: Installed on 2011-10-21 (692 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: libunity UpgradeStatus: Upgraded to raring on 2013-01-20 (234 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1224621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1204272] Re: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV()
*** This bug is a duplicate of bug 1194465 *** https://bugs.launchpad.net/bugs/1194465 ** This bug is no longer a duplicate of private bug 1201917 ** This bug has been marked a duplicate of private bug 1194465 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1204272 Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV() Status in “libunity” package in Ubuntu: New Bug description: Crash when searching "Synaptic" in Unity Dashboard. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.7+13.10.20130703.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.11-0ubuntu1 Architecture: i386 CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912 CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e Date: Tue Jul 23 23:05:00 2013 Dependencies: EcryptfsInUse: Yes ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/gdrive/unity_gdrive_daemon.py ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fr_FR:en PATH=(custom, user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0xb5162756:cmp%edi,(%eax) PC (0xb5162756) ok source "%edi" ok destination "(%eax)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libsignon-glib.so.1 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic (closure=0x880f1a0, return_gvalue=0x0, n_param_values=1, param_values=0x86eae20, invocation_hint=0xbff88bbc, marshal_data=0x0) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:1454 g_closure_invoke (closure=0x880f1a0, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0x86eae20, invocation_hint=invocation_hint@entry=0xbff88bbc) at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777 Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: Upgraded to saucy on 2013-05-25 (58 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1204272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868904] Re: Redshift fails to start with session due to geoclue failure
I can confirm this. After installing "geoclue-hostip" RedShift works. So it is a simple missing dependency issue. Package maintainter can fix this issue really fast... $ gtk-redshift Started Geoclue provider `Geoclue Master'. Using provider `geoclue'. Could not get location (3 retries left): Geoclue master client has no usable Position providers. Unable to get location from provider. $ sudo apt-get install geoclue-hostip $ gtk-redshift Started Geoclue provider `Geoclue Master'. Using provider `geoclue'. According to the geoclue provider we're at: 45.80, 15.78 Using method `randr'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/868904 Title: Redshift fails to start with session due to geoclue failure Status in Redshift color temperature adjustment: Confirmed Status in Ubuntu GeoIP Provider: New Status in “redshift” package in Ubuntu: Fix Released Status in “ubuntu-geoip” package in Ubuntu: Confirmed Bug description: Since switching to oneiric redshift won't start. It is listed as a startup application and these lines are present in .xsession-error from it: Unable to get location from provider. Started Geoclue provider `Geoclue Master'. Using provider `geoclue'. There is also no process in a ps listing. If I start it from the command prompt then it starts just fine often with substantially similar messages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: redshift 1.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Wed Oct 5 22:39:15 2011 SourcePackage: redshift UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/redshift/+bug/868904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1207434] Re: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString()
*** This bug is a duplicate of bug 1204310 *** https://bugs.launchpad.net/bugs/1204310 ** This bug is no longer a duplicate of bug 1206661 scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() ** This bug has been marked a duplicate of bug 1204310 scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1207434 Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() Status in “libunity” package in Ubuntu: New Bug description: help ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130723-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Jul 27 14:04:40 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py ExecutableTimestamp: 1374563432 InstallationDate: Installed on 2013-07-04 (22 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s news/googlenews.scope ProcCwd: /home/angel SegvAnalysis: Segfault happened at: 0x7ff4ab3c3c51:movdqu (%rdi),%xmm1 PC (0x7ff4ab3c3c51) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 PyUnicode_FromString () pyglib_error_marshal () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 pyglib_error_check () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() UpgradeStatus: Upgraded to saucy on 2013-07-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1207434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1204310] Re: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString()
Looks like a transient issue from older version of python-gobject. Please re-open if you experience this crash again. ** Changed in: libunity (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1204310 Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() Status in “libunity” package in Ubuntu: Fix Released Bug description: Error reported by apport on login ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130723-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Jul 23 18:13:29 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-06-17 (36 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130616) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s news/googlenews.scope ProcCwd: /home/jerome ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f544cca2711:movdqu (%rdi),%xmm1 PC (0x7f544cca2711) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 PyUnicode_FromString () pyglib_error_marshal () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 pyglib_error_check () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1204310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1206661] Re: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString()
*** This bug is a duplicate of bug 1204310 *** https://bugs.launchpad.net/bugs/1204310 Looks like a transient issue from older version of python-gobject. Please re-open if you experience this crash again. ** Changed in: libunity (Ubuntu) Status: Confirmed => Invalid ** This bug has been marked a duplicate of bug 1204310 scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1206661 Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() Status in “libunity” package in Ubuntu: Invalid Bug description: help ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.9+13.10.20130723-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Jul 27 14:04:40 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py ExecutableTimestamp: 1374563432 InstallationDate: Installed on 2013-07-04 (22 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s news/googlenews.scope ProcCwd: /home/angel SegvAnalysis: Segfault happened at: 0x7ff4ab3c3c51:movdqu (%rdi),%xmm1 PC (0x7ff4ab3c3c51) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 PyUnicode_FromString () pyglib_error_marshal () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 pyglib_error_check () from /usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python3.3.so.0 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so Title: scope-runner-dbus.py crashed with SIGSEGV in PyUnicode_FromString() UpgradeStatus: Upgraded to saucy on 2013-07-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1206661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195807] Re: Unity dash previews won't load
Previews are now loaded correctly with latest 13.10, therefore marking as Fix released. ** Changed in: libunity (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libunity Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1195807 Title: Unity dash previews won't load Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: I have this error in Ubuntu 13.04 and 13.10 (I also had it back in 12.10). Under the "more suggestions" in the video lens , the previews never load and it's just a spinning wheel for hours. A bug report window also pops up after about 10 seconds, and I'm finally reporting it. For Ubuntu 13.10, this same thing happens often for the smart scopes. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scopes-runner 7.0.4daily13.06.24-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-0.7-generic 3.10.0-rc7 Uname: Linux 3.10.0-0-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Jun 28 10:42:00 2013 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2013-06-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130627) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/soundcloud/unity_soundcloud_daemon.py ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f84f4f7311e:cmpq $0x4c,(%rax) PC (0x7f84f4f7311e) ok source "$0x4c" ok destination "(%rax)" (0x0009) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so PyEval_EvalFrameEx () PyEval_EvalCodeEx () PyEval_EvalFrameEx () Title: scope-runner-dbus.py crashed with SIGSEGV in PyEval_EvalFrameEx() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1195807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1235933] Re: Evolution not translated to French
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evolution (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1235933 Title: Evolution not translated to French Status in “evolution” package in Ubuntu: Confirmed Bug description: My desktop is set up in the French language, but Evolution is the only installed application to be displayed in English. Gnome-language- selector doesn't suggest to install any missing package though. This is after upgrading to Saucy. It was in French when running Raring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution 3.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sun Oct 6 13:25:49 2013 InstallationDate: Installed on 2010-09-15 (1116 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) MarkForUpload: True SourcePackage: evolution UpgradeStatus: Upgraded to saucy on 2011-04-01 (919 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1235933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171567] Re: Incorrect scope files/ids of some of the default scopes
** No longer affects: unity-lens-video (Ubuntu Raring) ** No longer affects: unity-lens-music (Ubuntu Raring) ** No longer affects: unity-lens-files (Ubuntu Raring) ** No longer affects: libunity (Ubuntu Raring) ** Changed in: unity-lens-files (Ubuntu) Status: New => Fix Released ** Changed in: unity-lens-music (Ubuntu) Status: New => Fix Released ** Changed in: libunity (Ubuntu) Status: New => Fix Released ** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: unity-lens-music Status: Fix Committed => Fix Released ** Changed in: unity-lens-video Status: Fix Committed => Fix Released ** Changed in: unity-lens-files Status: Fix Committed => Fix Released ** Changed in: unity-lens-video (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-lens-files in Ubuntu. Matching subscriptions: dp-libunity, dp-unity-lens-files, dp-unity-lens-music https://bugs.launchpad.net/bugs/1171567 Title: Incorrect scope files/ids of some of the default scopes Status in LibUnity: Fix Released Status in Unity: Invalid Status in Unity Files Lens: Fix Released Status in unity-lens-music: Fix Released Status in Unity Videos Lens: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “unity-lens-files” package in Ubuntu: Fix Released Status in “unity-lens-music” package in Ubuntu: Fix Released Status in “unity-lens-video” package in Ubuntu: Fix Released Bug description: Scope (.scope) files of some of the default scopes have incorrect names, leading to scope ids such as video-video-local.scope. Files that have this issue are files/files-local.scope music/music-rhythmbox.scope music/music-banshee.scope video/video-local.scope video/video-remote.scope To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1171567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902242] Re: Unity should provide an "active" signal on a per lens basis
Marking as invalid since the latest scope API doesn't have a active property, plus together with TTL of result set this should be considered fixed. ** No longer affects: unity ** Changed in: libunity (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libunity Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/902242 Title: Unity should provide an "active" signal on a per lens basis Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: The current notify::active signal is sent when the dash is opened, closed or when any lens is displayed. Lens developers using remote APIs need to be cautious with the number of API calls they send. When they need to display a default set of results when a lens is opened, they use this signal despite of it being sent a lot more than needed and triggering a lot of unwanted API calls. Unity should provide an "active" signal on a per lens basis. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/902242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1229295] Re: A4 Right margin cut off with HP Deskjet 5550
Once again, A4.SM/Evince was fine. Here's the Evince capture. ** Attachment added: "d00428-001" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+attachment/3879331/+files/d00428-001 -- 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/1229295 Title: A4 Right margin cut off with HP Deskjet 5550 Status in “cups” package in Ubuntu: Invalid Status in “okular” package in Ubuntu: Incomplete Bug description: Here is the example pdf file attached and also two photos of the printed page. I used RTL because it demonstrates better the edge that is cut off - the right edge. This is supposed to be an A4 PDF (the file is attached so you can check). And this is supposed to be an A4 (210x297) printout (the printer settings are that). Blessings, Shahar ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cups 1.7.0~rc1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Sep 23 19:46:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-10-12 (1077 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Lpstat: device for deskjet_5550: hp:/usb/deskjet_5550?serial=MY28A1R5B42L MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3 MarkForUpload: True Papersize: letter PpdFiles: deskjet_5550: HP Deskjet 5550, hpcups 3.13.8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=/dev/mapper/ssd-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to saucy on 2013-05-07 (138 days ago) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4c dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd12/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1229295] Re: A4 Right margin cut off with HP Deskjet 5550
And here's what came out of that. ** Attachment added: "d00430-001" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+attachment/3879333/+files/d00430-001 -- 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/1229295 Title: A4 Right margin cut off with HP Deskjet 5550 Status in “cups” package in Ubuntu: Invalid Status in “okular” package in Ubuntu: Incomplete Bug description: Here is the example pdf file attached and also two photos of the printed page. I used RTL because it demonstrates better the edge that is cut off - the right edge. This is supposed to be an A4 PDF (the file is attached so you can check). And this is supposed to be an A4 (210x297) printout (the printer settings are that). Blessings, Shahar ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cups 1.7.0~rc1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Sep 23 19:46:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-10-12 (1077 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Lpstat: device for deskjet_5550: hp:/usb/deskjet_5550?serial=MY28A1R5B42L MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3 MarkForUpload: True Papersize: letter PpdFiles: deskjet_5550: HP Deskjet 5550, hpcups 3.13.8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=/dev/mapper/ssd-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to saucy on 2013-05-07 (138 days ago) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4c dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd12/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220733] Re: OEM scope customization isn't working properly
** Changed in: libunity Status: Fix Committed => Fix Released ** Changed in: unity-scope-home Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-lens-applications in Ubuntu. Matching subscriptions: dp-unity-lens-music https://bugs.launchpad.net/bugs/1220733 Title: OEM scope customization isn't working properly Status in LibUnity: Fix Released Status in Unity Home Scope: Fix Released Status in “unity-lens-applications” package in Ubuntu: Fix Released Status in “unity-scope-home” package in Ubuntu: Fix Released Bug description: Currently if an OEM wants to customize which scopes are displayed and queried on the device, the only possibility for customization is to add a scope as a separate page, due to a bug in how home-scope discovers scopes. Also, we need a simple way for removing scopes without actually deleting them from the filesystem image. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1220733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1231390] Re: Creating SearchContext from python no longer accepts None for metadata
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1231390 Title: Creating SearchContext from python no longer accepts None for metadata Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: As this is a regression and breaks quite a few users, we should fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1231390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1235342] Re: libunity-tool doesn't parse scope files correctly
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1235342 Title: libunity-tool doesn't parse scope files correctly Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: Scope files that are using current GroupName and DBusName in their .scope files do not work with libunity-tool as it doesn't use the protocol library. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1235342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199715] Re: unity-scope-home crashed with signal 5 in g_wakeup_new()
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1199715 Title: unity-scope-home crashed with signal 5 in g_wakeup_new() Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “unity-scope-home” package in Ubuntu: Invalid Bug description: Not sure what happened here, just started my session. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity-scope-home 6.8.1+13.10.20130705-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Wed Jul 10 10:44:49 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home Signal: 5 SourcePackage: unity-scope-home StacktraceTop: g_wakeup_new () at /build/buildd/glib2.0-2.37.3/./glib/gwakeup.c:163 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x1ae22b0, pollfd=pollfd@entry=0x7f2580a21b20) at /build/buildd/glib2.0-2.37.3/./gio/gcancellable.c:402 socket_source_new (cancellable=0x1ae22b0, condition=(G_IO_IN | G_IO_ERR | G_IO_HUP), socket=0x1b09130) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3264 g_socket_create_source (socket=0x1b09130, condition=condition@entry=(G_IO_IN | G_IO_ERR | G_IO_HUP), cancellable=cancellable@entry=0x1ae22b0) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3329 _g_socket_read_with_control_messages (socket=0x1b09130, buffer=0x7f2580589f10, count=16, messages=0x1b0cb00, num_messages=0x1b0cb08, io_priority=, cancellable=0x1ae22b0, callback=0x7f258b2a6160 <_g_dbus_worker_do_read_cb>, user_data=0x1b0ca70) at /build/buildd/glib2.0-2.37.3/./gio/gdbusprivate.c:201 Title: unity-scope-home crashed with signal 5 in g_wakeup_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1199715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1229295] Re: A4 Right margin cut off with HP Deskjet 5550
I've noticed that Okular/KDE have this dialog with margins. So I tried printing again, as I did before, without changing the values. Here is the dialog. ** Attachment added: "okular.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+attachment/3879332/+files/okular.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1229295 Title: A4 Right margin cut off with HP Deskjet 5550 Status in “cups” package in Ubuntu: Invalid Status in “okular” package in Ubuntu: Incomplete Bug description: Here is the example pdf file attached and also two photos of the printed page. I used RTL because it demonstrates better the edge that is cut off - the right edge. This is supposed to be an A4 PDF (the file is attached so you can check). And this is supposed to be an A4 (210x297) printout (the printer settings are that). Blessings, Shahar ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cups 1.7.0~rc1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Sep 23 19:46:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-10-12 (1077 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Lpstat: device for deskjet_5550: hp:/usb/deskjet_5550?serial=MY28A1R5B42L MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3 MarkForUpload: True Papersize: letter PpdFiles: deskjet_5550: HP Deskjet 5550, hpcups 3.13.8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=/dev/mapper/ssd-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to saucy on 2013-05-07 (138 days ago) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4c dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd12/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1212307] Re: SearchContext.search_metadata is empty when creating it from python.
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1212307 Title: SearchContext.search_metadata is empty when creating it from python. Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: When a Unity.SearchContext is created from python, the search_metadata is always empty. Code to reproduce the issue: http://paste.ubuntu.com/5985211/ To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1212307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1222828] Re: unity-scope-loader doesn't handle missing modules correctly
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1222828 Title: unity-scope-loader doesn't handle missing modules correctly Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: unity-scope-loader doesn't correctly handle return value of GLib.Module.open(). If module is missing, it fails at a later stage when checking module version, which produces assertion errors on module != NULL and a misleading error about missing get_version function. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1222828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219792] Re: libunity-tool crashes when it can't connect to the bus
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1219792 Title: libunity-tool crashes when it can't connect to the bus Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: libunity-tool crashes when it can't connect to session bus (which is fairly often when ssh-ing into the device and forgetting to set the dbus envvar). To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1219792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 923727] Re: Unity lenses protocol causes excessive context switching
The latest protocol already has an option to use private connections, although they're not enabled for all channels by default, only the dash to master scope channel isn't using private connection. ** Changed in: libunity (Ubuntu) Status: Triaged => Fix Released ** Changed in: libunity Status: Triaged => Fix Released ** Changed in: unity Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/923727 Title: Unity lenses protocol causes excessive context switching Status in LibUnity: Fix Released Status in Unity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: Updating DeeModels is currently done over DBus which causes extra copies from lenses' processes to dbus-daemon and then to unity(-2d). Dee now supports private connections which allow us to skip the copy to dbus-daemon, we should use these for the lenses' models to get the issue under control. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/923727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170810] Re: unity.deps contains unnecessary API dependencies
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1170810 Title: unity.deps contains unnecessary API dependencies Status in Geary: Fix Committed Status in LibUnity: Fix Released Status in “libunity” package in Ubuntu: Fix Released Bug description: The unity.deps file (required for Vala compilation) includes gee-1.0 as a dependency. However, libgee is not used by the vapi and therefore should not be included. To quote from the Vala upstream bindings guide (from https://live.gnome.org/Vala/UpstreamGuide ) "The only other file that should be distributed is a deps file, which lists pkg-config names of any dependencies exposed in the public API." In other words, if there are no libgee symbols in the API, libgee shouldn't be included in the deps file. It's quite possible some of the other libraries aren't needed for the API as well, I haven't checked. This is a problem for us as it means we can't link against both libunity and libgee 0.8, since libunity's deps file causes Vala to pull in symbols for libgee 0.6, which causes the compiler to error out with a symbol conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/geary/+bug/1170810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1234282] Re: It's possible to add more than one U1 account from system settings on the phone
** Also affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New ** Also affects: accounts-qml-module (Ubuntu) Importance: Undecided Status: New ** Also affects: libaccounts-glib (Ubuntu) Importance: Undecided Status: New ** Also affects: libaccounts-qt (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntuone-credentials (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1234282 Title: It's possible to add more than one U1 account from system settings on the phone Status in Online Accounts setup for Ubuntu Touch: In Progress Status in Ubuntu One Credentials API: In Progress Status in “accounts-qml-module” package in Ubuntu: New Status in “libaccounts-glib” package in Ubuntu: New Status in “libaccounts-qt” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Status in “ubuntuone-credentials” package in Ubuntu: New Bug description: To reproduce: Open **System Settings**. Go to **Accounts**. On the **Add Account** section, select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. The **Accounts** screen is shown. Click **Add account...** Select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. After adding the first U1 account, the second time you click Add account, U1 should not be available as an option. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1234282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** Summary changed: - Can't set keyboard layout change to ctrl+shift + Can't set keyboard layout change to alt+shift, ctrl+shift, etc. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Indicator keyboard: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
Perhaps I spoke too soon. After rebooting I lost sound completely again. I tried: * Booting into Windows then booting into kernel 3.8 * Booting with kernel 3.8 with headphones plugged into the rear headphone jack. * Purging and reconfiguring alsa and delete asound's from /var/lib/alsa and rebooting * Booting with position fix off and on * Booting into kernel 3.11 with position fix off and on * Booting into kernel 3.11 with headphones plugged into the rear and front headphone jacks. Nothing works. Furthermore, apparently if I boot with kernel 3.11 there are about 6 error messages, two of which say permission error, and the screen is black with just the cursor for about 5 seconds before Unity decides to load. Half the time Ubuntu hangs when booting, so that's a major problem. Then if you use unity --replace & disown, unity will completely explode, then sometimes Qt programs just look horrible. I guess I'm going to have to stick with Ubuntu 13.04 on this machine. -- 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/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in The Linux Kernel: New Status in “alsa-driver” package in Ubuntu: Triaged Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX 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.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX: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/alsa-driver/+bug/1166529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240514] Re: users-admin crashed with SIGSEGV in g_type_check_instance_is_a()
*** This bug is a duplicate of bug 1221412 *** https://bugs.launchpad.net/bugs/1221412 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1221412, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1240514/+attachment/3879334/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1240514/+attachment/3879336/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1240514/+attachment/3879337/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1240514/+attachment/3879338/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1240514/+attachment/3879339/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1240514/+attachment/3879340/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1240514/+attachment/3879341/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1221412 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1240514 Title: users-admin crashed with SIGSEGV in g_type_check_instance_is_a() Status in “gnome-system-tools” package in Ubuntu: New Bug description: Opened User and Groups, went to manage groups and then close the manage groups and User and Group windows. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-system-tools 3.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 16 09:21:04 2013 ExecutablePath: /usr/bin/users-admin InstallationDate: Installed on 2013-07-28 (79 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130728) MarkForUpload: True ProcCmdline: users-admin ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f24421ccb3c : testb $0x4,0x16(%r8) PC (0x7f24421ccb3c) ok source "$0x4" ok destination "0x16(%r8)" (0x614d65766f6d6566) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-system-tools StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gst_user_profiles_get_for_user () user_settings_show () on_table_selection_changed () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: users-admin crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1240514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078379] Re: Jockey-KDE doesn't show drivers versions
It's too late for 13.10 and we'll be migrating to ubuntu-drivers for 14.04, so this is not something we intend to fix in Jockey. ** Changed in: jockey (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078379 Title: Jockey-KDE doesn't show drivers versions Status in “jockey” package in Ubuntu: Won't Fix Bug description: Jockey-KDE doesn't show the number versions of the available drivers. Only shows the name of the driver package installed (for example, nvidia-current or nvidia-experimental-304), but not the number version of the others. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: jockey-kde 0.9.7-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Nov 13 18:35:16 2012 InstallationDate: Installed on 2012-03-24 (234 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120319) MachineType: System manufacturer System Product Name MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=e26c2363-e5ed-4e90-90b1-d10604263206 ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: Upgraded to quantal on 2012-11-13 (0 days ago) dmi.bios.date: 08/26/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0509 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0509:bd08/26/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-SE:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1078379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240522] [NEW] automatic readjustment of column widths "flickering behaviuor"
Public bug reported: When going to a folder containing a lot of files/folders with different length of names, during build up of thumbnails (?) (10 sec. at least) in listmode the column width of "Name" changes rapidly. Also, when being in several subfolders of diferrent name lengths, and you want to click directly into several folders upwards, the whole line is readjusting rapidly making it impossible to use. It is hard to describe, it is a extremely annoying thing, happened only after updating to 13.04. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1240522 Title: automatic readjustment of column widths "flickering behaviuor" Status in “nautilus” package in Ubuntu: New Bug description: When going to a folder containing a lot of files/folders with different length of names, during build up of thumbnails (?) (10 sec. at least) in listmode the column width of "Name" changes rapidly. Also, when being in several subfolders of diferrent name lengths, and you want to click directly into several folders upwards, the whole line is readjusting rapidly making it impossible to use. It is hard to describe, it is a extremely annoying thing, happened only after updating to 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1240522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1234282] Re: It's possible to add more than one U1 account from system settings on the phone
Fix committed into lp:ubuntu-system-settings-online-accounts at revision 70, scheduled for release in ubuntu-system-settings-online-accounts, milestone Unknown ** Changed in: ubuntu-system-settings-online-accounts Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1234282 Title: It's possible to add more than one U1 account from system settings on the phone Status in Online Accounts setup for Ubuntu Touch: Fix Committed Status in Ubuntu One Credentials API: In Progress Status in “accounts-qml-module” package in Ubuntu: New Status in “libaccounts-glib” package in Ubuntu: New Status in “libaccounts-qt” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Status in “ubuntuone-credentials” package in Ubuntu: New Bug description: To reproduce: Open **System Settings**. Go to **Accounts**. On the **Add Account** section, select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. The **Accounts** screen is shown. Click **Add account...** Select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. After adding the first U1 account, the second time you click Add account, U1 should not be available as an option. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1234282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
** Changed in: gvfs (Ubuntu) Status: Confirmed => Triaged ** Changed in: gvfs (Ubuntu) Importance: Undecided => High -- 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/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Status in “gvfs” package in Debian: New Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** Branch linked: lp:~attente/gnome-control-center/lp1218322 -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Indicator keyboard: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1234282] Re: It's possible to add more than one U1 account from system settings on the phone
** Description changed: - To reproduce: + SRU information: + + [Impact] Accidental creation of multiple UbuntuOne accounts can compromise the functionality of U1 (whose stack does not support multiple accounts). + The fix consists in disabling (greying out) the "Ubuntu One" item when an account for it already exists. + + [Test Case] With these steps it's possible to create two U1 accounts: + Open **System Settings**. + Go to **Accounts**. + On the **Add Account** section, select **Ubuntu One**. + Enter the email address. + Enter the password. + Click **Continue**. + The **Accounts** screen is shown. + Click **Add account...** + Select **Ubuntu One**. + Enter the email address. + Enter the password. + Click **Continue**. + + [Regression Potential] Several packages are involved in this bugfix: + - ubuntuone-credentials: the only changes done here is the addition of a + "true" line in the ubuntuone.provider XML file. + This cannot cause any regression (and older versions of libaccounts-glib simply + ignore any unrecognized elements). + + - libaccounts-glib: added a new API to return the value of the + element; also here there's no risk of regression, as applications now using this + new API are unaffected. Besides, unit tests have been added to cover this API. + + - libaccounts-qt: this is just a thin wrapper around libaccounts-glib. So the same + API was added here, with unit tests. Other code paths are unaffected by this + change. + + - accounts-qml-module: this is a wrapper for libaccounts-qt, to provide a QML API. + The value of the element has been added as a role in the + ProvidersModel class. Again, this doesn't affect the existing functionality, is + well covered with unit tests and moreover at the current stage the ProvidersModel + class is known to be used only by the ubuntu-system-settings-online-accounts + project. + + - ubuntu-system-settings-online-accounts: support for reading the value + (via accounts-qml-module) and if that is true, then check if there are already some + accounts created for the given provider. The code changes consists in about 10 lines + of code, and all but one are only triggered if the flag is true + (which happens for the U1 provider only). The code has been tested and works. + + = + Original description: + Open **System Settings**. Go to **Accounts**. On the **Add Account** section, select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. The **Accounts** screen is shown. Click **Add account...** Select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. After adding the first U1 account, the second time you click Add account, U1 should not be available as an option. See the attached screenshot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1234282 Title: It's possible to add more than one U1 account from system settings on the phone Status in Online Accounts setup for Ubuntu Touch: Fix Committed Status in Ubuntu One Credentials API: In Progress Status in “accounts-qml-module” package in Ubuntu: New Status in “libaccounts-glib” package in Ubuntu: New Status in “libaccounts-qt” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Status in “ubuntuone-credentials” package in Ubuntu: New Bug description: SRU information: [Impact] Accidental creation of multiple UbuntuOne accounts can compromise the functionality of U1 (whose stack does not support multiple accounts). The fix consists in disabling (greying out) the "Ubuntu One" item when an account for it already exists. [Test Case] With these steps it's possible to create two U1 accounts: Open **System Settings**. Go to **Accounts**. On the **Add Account** section, select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. The **Accounts** screen is shown. Click **Add account...** Select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. [Regression Potential] Several packages are involved in this bugfix: - ubuntuone-credentials: the only changes done here is the addition of a "true" line in the ubuntuone.provider XML file. This cannot cause any regression (and older versions of libaccounts-glib simply ignore any unrecognized elements). - libaccounts-glib: added a new API to return the value of the element; also here there's no risk of regression, as applications now using this new API are unaffected. Besides, unit tests have been added to cover this API. - libaccounts-qt: this is just a thin wrapper around libaccounts-glib. So the same API was added here, with unit tests. Other code paths are unaffected by this change.
[Desktop-packages] [Bug 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
Upstream has been pinged about the issue, let's see what they say about it -- 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/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Status in “gvfs” package in Debian: New Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240531] [NEW] gnome-settings-daemon crashed with SIGSEGV
Public bug reported: This crash occurred soon after an oem installation of saucy desktop i386 image of 20131016. Steps: 1. Perform and oem installation 2. Reboot after the installation. 3. This crash was reported soon after the reboot. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Wed Oct 16 14:53:23 2013 Disassembly: => 0xb6f10040: Cannot access memory at address 0xb6f10040 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ExecutableTimestamp: 1381919282 InstallationDate: Installed on 2013-10-16 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCwd: /var/lib/lightdm ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0xb6f10040: Cannot access memory at address 0xb6f10040 PC (0xb6f10040) ok SP (0xbfd5d070) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-settings-daemon Stacktrace: #0 0xb6f10040 in ?? () No symbol table info available. StacktraceTop: ?? () Title: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace rls-s-incoming saucy ** Information type changed from Private to Public -- 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/1240531 Title: gnome-settings-daemon crashed with SIGSEGV Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: This crash occurred soon after an oem installation of saucy desktop i386 image of 20131016. Steps: 1. Perform and oem installation 2. Reboot after the installation. 3. This crash was reported soon after the reboot. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Wed Oct 16 14:53:23 2013 Disassembly: => 0xb6f10040: Cannot access memory at address 0xb6f10040 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ExecutableTimestamp: 1381919282 InstallationDate: Installed on 2013-10-16 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCwd: /var/lib/lightdm ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0xb6f10040:Cannot access memory at address 0xb6f10040 PC (0xb6f10040) ok SP (0xbfd5d070) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-settings-daemon Stacktrace: #0 0xb6f10040 in ?? () No symbol table info available. StacktraceTop: ?? () Title: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1240531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1072508] Re: lens process keep running after logout
** Tags removed: verification-failed
** Changed in: unity-lens-applications
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
Matching subscriptions: dp-unity, dp-unity-lens-files, dp-unity-lens-music,
dp-unity-lens-music
https://bugs.launchpad.net/bugs/1072508
Title:
lens process keep running after logout
Status in GVFS:
Fix Released
Status in The Ubuntu Power Consumption Project:
Confirmed
Status in Unity:
Invalid
Status in Unity Applications Lens:
Invalid
Status in Unity Files Lens:
Confirmed
Status in unity-lens-music:
Confirmed
Status in “gvfs” package in Ubuntu:
Fix Released
Status in “unity” package in Ubuntu:
Invalid
Status in “unity-lens-applications” package in Ubuntu:
Confirmed
Status in “unity-lens-files” package in Ubuntu:
Confirmed
Status in “unity-lens-music” package in Ubuntu:
Confirmed
Status in “gvfs” source package in Quantal:
Fix Committed
Status in “unity” source package in Quantal:
Confirmed
Status in “unity-lens-applications” source package in Quantal:
Confirmed
Status in “unity-lens-files” source package in Quantal:
Confirmed
Status in “unity-lens-music” source package in Quantal:
Confirmed
Bug description:
* Impact:
Some process, like unity-{application,files,music}-daemon, keep running after
user log out.
* Test Case:
1) login on Unity session
2) open the dash
3) check in system monitor: one instance per process -eg, 1
unity-application-daemon
4) logout
5) repeat steps 1-3. Now there's 2 proccess called unity-application-daemon
if you keep repeating the steps, the number of process increase.
* Regression potential:
the update which contains the fix has a few changes, check that gvfs keeps
working file (try browsing different remote locations from nautilus, use the
dash to search for online music and videos, ...)
This also affects some other process, like 3rd party unity-lens-{torrents,
wikipedia}. Scopes are not affected.
As a result, memory footprint after login in increases.
I'm running Ubuntu 12.10, up-to-date. Unity 6.8.0-0ubuntu2.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: unity 6.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sun Oct 28 20:14:25 2012
InstallationDate: Installed on 2012-10-19 (9 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1072508/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1197328] Re: gvfsd-obexftp crashed with SIGSEGV in dbus_g_proxy_call()
** Tags added: bot-stop-nagging -- 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/1197328 Title: gvfsd-obexftp crashed with SIGSEGV in dbus_g_proxy_call() Status in “gvfs” package in Ubuntu: New Bug description: Bug in bluetooth stack or application. I wanted to send files and it crashed. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gvfs-backends 1.14.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 ApportVersion: 2.6.1-0ubuntu12 Architecture: amd64 Date: Wed Jul 3 11:56:03 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-obexftp InstallationDate: Installed on 2013-02-18 (134 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-obexftp --spawner :1.7 /org/gtk/gvfs/exec_spaw/2 ProcCwd: / ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=pl_PL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3e27e0c69c : testb $0x4,0x16(%rdi) PC (0x7f3e27e0c69c) ok source "$0x4" ok destination "0x16(%rdi)" (0x0192) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: gvfs StacktraceTop: g_type_check_instance_is_a (type_instance=type_instance@entry=0x22be2c0, iface_type=iface_type@entry=36440464) at /build/buildd/glib2.0-2.34.1/./gobject/gtype.c:3964 dbus_g_proxy_call (proxy=0x22be2c0, method=method@entry=0x41ed12 "ChangeCurrentFolderToRoot", error=error@entry=0x7f3e24c4bd68, first_arg_type=first_arg_type@entry=0) at dbus-gproxy.c:2746 _change_directory (op_backend=op_backend@entry=0x22c10e0, filename=filename@entry=0x22d0ed0 "link-target", error=error@entry=0x7f3e24c4bd68) at gvfsbackendobexftp.c:591 do_enumerate (backend=0x22c10e0, job=0x22bea20, filename=0x22d0ed0 "link-target", matcher=, flags=) at gvfsbackendobexftp.c:1507 g_vfs_job_run (job=0x22bea20) at gvfsjob.c:197 Title: gvfsd-obexftp crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1197328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240530] [NEW] software-center crashed with signal 5 in _XReadEvents()
*** This bug is a duplicate of bug 1211887 *** https://bugs.launchpad.net/bugs/1211887 Public bug reported: Software center seems to crash on the first launch after install. I hit this on the saucy rc image from 20131016 The install I had done was amd64 desktop on virtualbox with free software only, no network connection. Once booted after installing, I attached the network, brought up a terminal and ran apt-get update. Everything looked fine, so I tried running software center and hit this crash. Running a second time, software center seems to come up ok though. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 16 09:54:54 2013 ExecutablePath: /usr/share/software-center/software-center ExecutableTimestamp: 1381335773 InstallationDate: Installed on 2013-10-16 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcCwd: /home/a ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: software-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 cairo_surface_flush () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: software-center crashed with signal 5 in _XReadEvents() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash rls-s-incoming saucy ** Information type changed from Private to Public -- 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/1240530 Title: software-center crashed with signal 5 in _XReadEvents() Status in “software-center” package in Ubuntu: New Bug description: Software center seems to crash on the first launch after install. I hit this on the saucy rc image from 20131016 The install I had done was amd64 desktop on virtualbox with free software only, no network connection. Once booted after installing, I attached the network, brought up a terminal and ran apt-get update. Everything looked fine, so I tried running software center and hit this crash. Running a second time, software center seems to come up ok though. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 16 09:54:54 2013 ExecutablePath: /usr/share/software-center/software-center ExecutableTimestamp: 1381335773 InstallationDate: Installed on 2013-10-16 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcCwd: /home/a ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: software-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 cairo_surface_flush () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: software-center crashed with signal 5 in _XReadEvents() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1240530/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240530] Re: software-center crashed with signal 5 in _XReadEvents()
*** This bug is a duplicate of bug 1211887 *** https://bugs.launchpad.net/bugs/1211887 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1211887, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1240530/+attachment/3879379/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1240530/+attachment/3879381/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1240530/+attachment/3879382/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1240530/+attachment/3879383/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1240530/+attachment/3879384/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1240530/+attachment/3879385/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1240530/+attachment/3879386/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1211887 ** Tags removed: need-amd64-retrace -- 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/1240530 Title: software-center crashed with signal 5 in _XReadEvents() Status in “software-center” package in Ubuntu: New Bug description: Software center seems to crash on the first launch after install. I hit this on the saucy rc image from 20131016 The install I had done was amd64 desktop on virtualbox with free software only, no network connection. Once booted after installing, I attached the network, brought up a terminal and ran apt-get update. Everything looked fine, so I tried running software center and hit this crash. Running a second time, software center seems to come up ok though. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-center 13.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 16 09:54:54 2013 ExecutablePath: /usr/share/software-center/software-center ExecutableTimestamp: 1381335773 InstallationDate: Installed on 2013-10-16 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcCwd: /home/a ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: software-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 cairo_surface_flush () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: software-center crashed with signal 5 in _XReadEvents() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1240530/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 667877] Re: application icon remains after apt-get remove
This is a very old bug and it's certainly not a case anymore with unity- lens-applications. Closing. ** Changed in: unity-lens-applications Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/667877 Title: application icon remains after apt-get remove Status in Unity: Incomplete Status in Unity 2D: Expired Status in Unity Applications Lens: Invalid Status in “unity” package in Ubuntu: Expired Status in “unity-place-applications” package in Ubuntu: Expired Bug description: Using Maverick. I see an icon for, say, inkscape, in the "Applications" menu. I apt-get remove inkscape. I re-open the Applications page, and I still see the inkscape icon, which is still clickable. I can click it, and the Applications menu goes away, making me think that it's trying to launch something, but of course, the app doesn't launch (since it's been removed). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/667877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236965] Re: [pulseaudio-discuss] [PATCH] alsa-mixer: Add internal surround speaker elements
On 10/14/2013 04:38 PM, Tanu Kaskinen wrote:
> On Mon, 2013-10-14 at 16:16 +0200, David Henningsson wrote:
>> +[Element Speaker CLFE]
>> +switch = mute
>> +volume = merge
>> +override-map.1 = all-center
>> +override-map.2 = all-center,lfe
>> +
>> .include analog-output.conf.common
>
> Should these elements be muted in other paths?
Good point. I've just added that and sent out a v2.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
--
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/1236965
Title:
pulseaudio does not recognize internal speakers [P180HMx, Realtek
ALC892, Speaker, Internal] volume slider problem
Status in “linux” package in Ubuntu:
Fix Committed
Status in “pulseaudio” package in Ubuntu:
In Progress
Bug description:
steps to reproduce:
1. acquire a device with the problem, such as Clevo P180HM laptop
motherboard
2. install ubuntu 12.04 (now updated to 12.04.3 currently)
3. systray > speaker-icon > sound-settings > output tab
4. no entry for "speakers built-in audio" appears
workaround:
running the shell script mentioned in this comment helps --
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/comments/158
however, the workaround is not completely satisfactory, because
adjusting the (singular) volume-slider provided by pulseaudio only
causes some of the (multiple) volume-sliders known to alsamixer to react.
Specifically, turning the pulseaudio volume upwards only changes the
'master' and belatedly the 'pcm' volumes inside alsamixer. This ignores
'speaker clfe' + 'speaker front' + 'speaker surround playback volume'
plus maybe others. Effectively, this means audio playback is weak: instead
of spreading typical 2ch audiofiles across all internal speakers, only some
are used, and only at whatever volume alsamixer specifies. (Turning the
ignored volumes up in alsamixer causes a different problem: then it is no
longer possible to lower the sound to a relatively-quiet volume.)
Here is some information from one of the ubuntu pulseaudio/alsa devs:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/comments/159
David Henningsson (946...@bugs.launchpad.net) wrote:
...you have unusual hardware: in addition to normal
headphones and stereo line out, you have 5.1 internal speakers. This
leads to unusual alsamixer names (e g "Speaker Front") which we do not
match for in PulseAudio. Fixing that means that we should add those
names in PulseAudio - but let's discuss that in a new bug instead.
Let me know if you would like more specifics. I have run codecgraph,
alsa-info, etc.
$ cat /proc/asound/card*/codec#* | grep --before-context=4 --after-context=1
"Subsystem Id"
Codec: Realtek ALC892
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0892
Subsystem Id: 0x15588000
Revision Id: 0x100302
--
Codec: ATI R6xx HDMI
Address: 0
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x1002aa01
Subsystem Id: 0x00aa0100
Revision Id: 0x100200
$ lspci -vvnn | grep --after-context=1 "Audio device"
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: CLEVO/KAPOK Computer Device [1558:8000]
--
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Barts
HDMI Audio [Radeon HD 6800 Series] [1002:aa88]
Subsystem: CLEVO/KAPOK Computer Device [1558:8000]
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-41.64~precise1-generic 3.5.7.21
Uname: Linux 3.5.0-41-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: j 6328 F pulseaudio
/dev/snd/controlC0: j 6328 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f0 irq 52'
Mixer name : 'Realtek ALC892'
Components : 'HDA:10ec0892,15588000,00100302'
Controls : 36
Simple ctrls : 16
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xf7e4 irq 54'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 6
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Oct 8 12:02:44 2013
InstallationMedia: This
MarkForUpload: True
PackageArchitect
[Desktop-packages] [Bug 1229295] Re: A4 Right margin cut off with HP Deskjet 5550
And the photo ** Attachment added: "IMG_20131016_162550.jpg" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+attachment/3879398/+files/IMG_20131016_162550.jpg -- 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/1229295 Title: A4 Right margin cut off with HP Deskjet 5550 Status in “cups” package in Ubuntu: Invalid Status in “okular” package in Ubuntu: Incomplete Bug description: Here is the example pdf file attached and also two photos of the printed page. I used RTL because it demonstrates better the edge that is cut off - the right edge. This is supposed to be an A4 PDF (the file is attached so you can check). And this is supposed to be an A4 (210x297) printout (the printer settings are that). Blessings, Shahar ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cups 1.7.0~rc1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CupsErrorLog: Date: Mon Sep 23 19:46:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-10-12 (1077 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Lpstat: device for deskjet_5550: hp:/usb/deskjet_5550?serial=MY28A1R5B42L MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3 MarkForUpload: True Papersize: letter PpdFiles: deskjet_5550: HP Deskjet 5550, hpcups 3.13.8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic root=/dev/mapper/ssd-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to saucy on 2013-05-07 (138 days ago) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4c dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd12/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 981212]
The ACPI for that laptop seems pretty broken: POWER_SUPPLY_CHARGE_NOW=-1000 You should report this as a bug against the kernel at bugzilla.kernel.org. The laptop lacks energy_* information. Reopen this bug if the kernel developers think that this is actually a bug in UPower. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/981212 Title: upower reports "percentage: 0%" while laptop is AC-adapter-powered and battery is 100% charged Status in Indicator Applet: Invalid Status in Upower: Won't Fix Status in “upower” package in Ubuntu: New Bug description: When laptop is powered by AC-adapter (with fully charged battery attached), battery menu indicates "Battery (not present)", which is confusing; when battery is discharging (or charging), it shows time left to full discharge (or full charge), and it's OK. I propose to use some label like "Battery (not active)" when laptop is AC-adapter-powered (and battery isn't charging). "Battery (not present)" should be used only when there's no battery detected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-applet-complete 0.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 14 01:11:48 2012 SourcePackage: indicator-applet UpgradeStatus: Upgraded to precise on 2012-03-07 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/981212/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 782953] Re: Software Center doesn't detect changes in sources until update-apt-xapian-index is ran by cron
** Branch linked: lp:software-properties -- 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/782953 Title: Software Center doesn't detect changes in sources until update-apt- xapian-index is ran by cron Status in “software-center” package in Ubuntu: Triaged Bug description: software-center 4.0.1, Ubuntu 11.04 For example, I add "ppa:hotot-team/ppa" to sources, and when I close the sources window, Software Center automatically starts updating repositories, but after that, doesn't appear on the left panel, I have to close Software Center, open it again, and now the new PPA is appearing. The equivalent for removing a PPA is bug 574155. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/782953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1234282] Re: It's possible to add more than one U1 account from system settings on the phone
** Changed in: ubuntuone-credentials Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1234282 Title: It's possible to add more than one U1 account from system settings on the phone Status in Online Accounts setup for Ubuntu Touch: Fix Committed Status in Ubuntu One Credentials API: Fix Committed Status in “accounts-qml-module” package in Ubuntu: New Status in “libaccounts-glib” package in Ubuntu: New Status in “libaccounts-qt” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Status in “ubuntuone-credentials” package in Ubuntu: New Bug description: SRU information: [Impact] Accidental creation of multiple UbuntuOne accounts can compromise the functionality of U1 (whose stack does not support multiple accounts). The fix consists in disabling (greying out) the "Ubuntu One" item when an account for it already exists. [Test Case] With these steps it's possible to create two U1 accounts: Open **System Settings**. Go to **Accounts**. On the **Add Account** section, select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. The **Accounts** screen is shown. Click **Add account...** Select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. [Regression Potential] Several packages are involved in this bugfix: - ubuntuone-credentials: the only changes done here is the addition of a "true" line in the ubuntuone.provider XML file. This cannot cause any regression (and older versions of libaccounts-glib simply ignore any unrecognized elements). - libaccounts-glib: added a new API to return the value of the element; also here there's no risk of regression, as applications now using this new API are unaffected. Besides, unit tests have been added to cover this API. - libaccounts-qt: this is just a thin wrapper around libaccounts-glib. So the same API was added here, with unit tests. Other code paths are unaffected by this change. - accounts-qml-module: this is a wrapper for libaccounts-qt, to provide a QML API. The value of the element has been added as a role in the ProvidersModel class. Again, this doesn't affect the existing functionality, is well covered with unit tests and moreover at the current stage the ProvidersModel class is known to be used only by the ubuntu-system-settings-online-accounts project. - ubuntu-system-settings-online-accounts: support for reading the value (via accounts-qml-module) and if that is true, then check if there are already some accounts created for the given provider. The code changes consists in about 10 lines of code, and all but one are only triggered if the flag is true (which happens for the U1 provider only). The code has been tested and works. = Original description: Open **System Settings**. Go to **Accounts**. On the **Add Account** section, select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. The **Accounts** screen is shown. Click **Add account...** Select **Ubuntu One**. Enter the email address. Enter the password. Click **Continue**. After adding the first U1 account, the second time you click Add account, U1 should not be available as an option. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1234282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
