[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
Issue is in pidgin way of using depracated signal(2) and threads and forking with a race condition. Fix is commited for pidgin 3.0. See https://hg.pidgin.im/pidgin/main/rev/161320946afd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37) plugins: probing /usr/lib/purple-2/simfix.so (16:52:37) plugins: probing /usr/lib/purple-2/libstatusnet.so (16:52:37) twitterim: plugin_init (16:52:37) twitterim: plugin = 0x7f658884bd30 (16:52:37) plugins: probing /usr/lib/purple-2/oldlogger.so (16:52:37) plugins: probing /usr/lib/purple-2/autoprofile.so (16:52:37) autoprofile: general: Initializing AutoProfile
[Desktop-packages] [Bug 962232] Re: Edit items in the Hardware section
** Changed in: gnome-control-center Status: New = Confirmed -- 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/962232 Title: Edit items in the Hardware section Status in GNOME Control Center: Confirmed Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: In the Details pane Overview section of the control center. the items should be reversed in order to show the CPU first. It may also be useful to indicate which graphics card you are using. See screenshot attached (screenshot is for system monitor, but the reordering stands for control center too) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/962232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170654] Re: Xorg freeze
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1170654 Title: Xorg freeze Status in “xorg” package in Ubuntu: Confirmed Bug description: Display freezes once or twice a day (have seen it mostly when using chrome), mouse can be moved but not able click on anything. Further when the issue occurs not able to switch to terminal (Ctrl + Alt + F1). Issue started occurring only after a Ubuntu update (Kernel 3.2.0-39+). If any ssh logs or more debugging is needed please request. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,resize,animation,workarounds,move,gnomecompat,imgpng,mousepoll,grid,snap,wall,place,vpswitch,unitymtgrabhandles,expo,session,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz Date: Fri Apr 19 06:22:11 2013 DistUpgraded: 2012-04-27 04:49:48,715 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21ce] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: LENOVO 4177CTO MarkForUpload: True ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-40-generic root=UUID=478a278b-dcf5-4f8b-8e3a-3d04f592c44a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to precise on 2012-04-27 (357 days ago) dmi.bios.date: 05/17/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET57WW (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu0.2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1170654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170232] Re: won't show login screen
Both X and lightdm are reporting a normal shutdown. Can you please attach ~/.xsession-errors and see if you can find a log file for unity? -- 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/1170232 Title: won't show login screen Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: If I plug in and and remove an external monitor it will make the login manager show up. Also, random crashes happen while using flash for youtube. [ 4611.400871] [ cut here ] [ 4611.400933] WARNING: at /build/buildd/linux-3.8.0/drivers/gpu/drm/i915/intel_display.c:7879 intel_modeset_check_state+0x4bb/0x610 [i915]() [ 4611.400937] Hardware name: Dell System XPS L321X [ 4611.400941] encoder's hw state doesn't match sw tracking (expected 1, found 0) [ 4611.400944] Modules linked in: hid_generic hidp hid joydev(F) snd_hda_codec_hdmi snd_hda_codec_realtek btusb uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev coretemp kvm_intel kvm ghash_clmulni_intel(F) aesni_intel(F) snd_hda_intel aes_x86_64(F) xts(F) lrw(F) snd_hda_codec gf128mul(F) ablk_helper(F) cryptd(F) snd_hwdep(F) dell_wmi sparse_keymap snd_pcm(F) dell_laptop snd_page_alloc(F) dcdbas snd_seq_midi(F) snd_seq_midi_event(F) snd_rawmidi(F) arc4(F) iwldvm snd_seq(F) mac80211 i915 snd_seq_device(F) snd_timer(F) drm_kms_helper iwlwifi drm cfg80211 microcode(F) psmouse(F) wmi serio_raw(F) lpc_ich i2c_algo_bit snd(F) video(F) soundcore(F) mei bnep rfcomm parport_pc(F) bluetooth ppdev(F) mac_hid binfmt_misc(F) lp(F) parport(F) ahci(F) libahci(F) [ 4611.401037] Pid: 1128, comm: Xorg Tainted: GF3.8.0-19-generic #29-Ubuntu [ 4611.401040] Call Trace: [ 4611.401055] [810587ef] warn_slowpath_common+0x7f/0xc0 [ 4611.401062] [810588ec] warn_slowpath_fmt+0x4c/0x50 [ 4611.401096] [a028af3f] ? intel_dp_get_hw_state+0x3f/0x1b0 [i915] [ 4611.401124] [a0281e1b] intel_modeset_check_state+0x4bb/0x610 [i915] [ 4611.401148] [a0281fb0] intel_connector_dpms+0x40/0x70 [i915] [ 4611.401176] [a01da990] drm_mode_obj_set_property_ioctl+0x330/0x340 [drm] [ 4611.401197] [a01da9d0] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm] [ 4611.401216] [a01c9559] drm_ioctl+0x4e9/0x5b0 [drm] [ 4611.401237] [a01da9a0] ? drm_mode_obj_set_property_ioctl+0x340/0x340 [drm] [ 4611.401247] [8117c788] ? kfree+0x28/0x110 [ 4611.401257] [81085bca] ? lg_local_unlock+0x1a/0x20 [ 4611.401265] [811b2dc9] ? mntput_no_expire+0x49/0x160 [ 4611.401273] [811a5919] do_vfs_ioctl+0x99/0x570 [ 4611.401280] [8119566e] ? fput+0xe/0x10 [ 4611.401288] [8107a08c] ? task_work_run+0xac/0xe0 [ 4611.401295] [811a5e81] sys_ioctl+0x91/0xb0 [ 4611.401305] [816d379d] system_call_fastpath+0x1a/0x1f [ 4611.401310] ---[ end trace e31434c46e2cf4ed ]--- [ 4611.401381] [ cut here ] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Apr 18 02:38:59 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationDate: Installed on 2013-04-14 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) MachineType: Dell Inc. Dell System XPS L321X MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=30632104-1e70-4ff2-a30d-d5b00279085d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 03/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0Y4RM9 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.:bvrA03:bd03/13/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn0Y4RM9:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.15-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1
[Desktop-packages] [Bug 1169836] Re: [Asus U50F, Intel IbexPeak HDMI, Digital Out, HDMI] No sound hdmi output
I just did an upgrade to 3.8.0-19 kernel and the problem persists, no hdmi output in sound settings, speaker-test not working for hdmi. -- 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/1169836 Title: [Asus U50F, Intel IbexPeak HDMI, Digital Out, HDMI] No sound hdmi output Status in The Linux Kernel: New Status in “alsa-driver” package in Ubuntu: New Bug description: I am running ubuntu raring ringtail 13.04(development branch). With the kernel upgrade, from 3.8.0-17 to 3.8.0-18 I have lost the option of choosing to play the sound through hdmi output, running ubuntu with the previous kernel solves the problem. speaker-test does not work with the hdmi output also. linux-image-extra-3.8.0-18-generic: Installed: 3.8.0-18.28 Candidate: 3.8.0-18.28 Version table: *** 3.8.0-18.28 0 500 http://pl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status linux-image-3.8.0-18-generic: Installed: 3.8.0-18.28 Candidate: 3.8.0-18.28 Version table: *** 3.8.0-18.28 0 500 http://pl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status linux-image-3.8.0-18-lowlatency: Installed: (none) Candidate: 3.8.0-18.12 Version table: 3.8.0-18.12 0 500 http://pl.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sasza 2600 F pulseaudio Date: Wed Apr 17 08:24:33 2013 InstallationDate: Installed on 2013-02-21 (54 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130221.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sasza 2600 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [hostname, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U50F.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U50F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU50F.202:bd11/27/2009:svnASUSTeKComputerInc.:pnU50F:pvr1.0:rvnASUSTeKComputerInc.:rnU50F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U50F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1169836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097903] Re: lightdm-session fails if user's .profile has non-posix sh init.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- 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/1097903 Title: lightdm-session fails if user's .profile has non-posix sh init. Status in “lightdm” package in Ubuntu: Confirmed Bug description: I don't actually mind the failure (its a feature!) The problem is that if the user's .profile has non-posix sh in it (causing /usr/sbin /lightdm-session to basically crash) there is no good presentation to the user about this. The user tries to login. Lightdm tries to source their ~/.profile, and crashes if they have non-posix sh in them. lightdm simply restarts and drops the user back at the login screen. There is no reporting to the user what happened, so they can fix the problem. What is worse, is that the failsafe session doesn't work either. -A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1097903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1077972] Re: doc-base files refer to non existent files
This bug still exists in raring (the package version did not change). ** Tags removed: quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1077972 Title: doc-base files refer to non existent files Status in “gstreamer0.10” package in Ubuntu: New Bug description: Here is the problem: # install-docs --install-all Unregistering 249 doc-base files, re-registering 252 doc-base files... Error in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: all `Format' sections are invalid. Error in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: all `Format' sections are invalid. Error in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above errors. Registering documents with scrollkeeper... # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-faq Warning in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: file `/usr/share/doc/gstreamer0.10-doc/faq/html/index.html' does not exist. Error in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: all `Format' sections are invalid. /usr/share/doc-base/gstreamer-0.10-faq: Fatal error found, the file won't be registered. # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-pwg Warning in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: file `/usr/share/doc/gstreamer0.10-doc/pwg/html/index.html' does not exist. Error in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: all `Format' sections are invalid. /usr/share/doc-base/gstreamer-0.10-pwg: Fatal error found, the file won't be registered. # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-manual Warning in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: file `/usr/share/doc/gstreamer0.10-doc/manual/html/index.html' does not exist. Error in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: all `Format' sections are invalid. /usr/share/doc-base/gstreamer-0.10-manual: Fatal error found, the file won't be registered. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gstreamer0.10-doc 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.18-lowlatency 3.5.7 Uname: Linux 3.5.0-18-lowlatency i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Mon Nov 12 15:59:43 2012 EcryptfsInUse: Yes MarkForUpload: True PackageArchitecture: all SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1077972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097903] Re: lightdm-session fails if user's .profile has non-posix sh init.
Seems like the other issue is that the default .profile sources .bashrc if $BASH_VERSION is set. But $BASH_VERSION is set even if bash is invoked as /bin/sh. .bashrc is designed only for sourcing by bash, not bash in posix mode, or any other shell, given that bash itself does not source .bashrc by default in that mode. A thought is it should do if [ -n $BASH_VERSION ] [ -n $POSIXLY_CORRECT ]; then # include .bashrc if it exists if [ -f $HOME/.bashrc ]; then . $HOME/.bashrc fi fi but your point is still valid: lightdm could handle the user's shell exiting much better. -- 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/1097903 Title: lightdm-session fails if user's .profile has non-posix sh init. Status in “lightdm” package in Ubuntu: Confirmed Bug description: I don't actually mind the failure (its a feature!) The problem is that if the user's .profile has non-posix sh in it (causing /usr/sbin /lightdm-session to basically crash) there is no good presentation to the user about this. The user tries to login. Lightdm tries to source their ~/.profile, and crashes if they have non-posix sh in them. lightdm simply restarts and drops the user back at the login screen. There is no reporting to the user what happened, so they can fix the problem. What is worse, is that the failsafe session doesn't work either. -A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1097903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063654] Re: yelp crashed with SIGSEGV in yelp_application_command_line()
This bug is fixed in raring. ** Changed in: yelp (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1063654 Title: yelp crashed with SIGSEGV in yelp_application_command_line() Status in “yelp” package in Ubuntu: Fix Released Bug description: yelp crashes with SIGSEGV upon invocation. There are 2 duplicate bugs, but I'm reporting this one because it occurs when more recent packages and will allow for apport retrace. I will merge them... ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: yelp 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.16-lowlatency 3.5.5 Uname: Linux 3.5.0-17-lowlatency i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 11:28:53 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/yelp ProcCmdline: yelp SegvAnalysis: Segfault happened at: 0x804c357: repz cmpsb %es:(%edi),%ds:(%esi) PC (0x0804c357) ok source %es:(%edi) (0x080508d8) ok destination %ds:(%esi) (0x007b) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: yelp StacktraceTop: ?? () 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_va (closure=0x9fa8ba8, return_value=0xbf9b86d4, instance=0x9fab800, args_list=0xbf9b883c , marshal_data=0x804c2d0, n_params=1, param_types=0x9fa95e0) at /build/buildd/glib2.0-2.34.0/./gobject/gclosure.c:1550 g_type_class_meta_marshalv (closure=closure@entry=0x9fa8ba8, return_value=return_value@entry=0xbf9b86d4, instance=instance@entry=0x9fab800, args=args@entry=0xbf9b883c , marshal_data=marshal_data@entry=0x50, n_params=n_params@entry=1, param_types=param_types@entry=0x9fa95e0) at /build/buildd/glib2.0-2.34.0/./gobject/gclosure.c:997 Title: yelp crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin plugdev pulse pulse-access scanner staff video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1063654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: jpeg images are washed out or colors are skewed
To anyone still affected by this: GNOME Color Manager developers are interested in verifying your autogenerated display color profiles. See https://bugzilla.gnome.org/show_bug.cgi?id=675645#c11 and http://blog.pcode.nl/2013/04/14/display-profiles-generated-from-edid/ ** Bug watch added: GNOME Bug Tracker #675645 https://bugzilla.gnome.org/show_bug.cgi?id=675645 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: jpeg images are washed out or colors are skewed Status in Eye of GNOME: New Status in “eog” package in Ubuntu: Confirmed Status in “eog” source package in Precise: Confirmed Bug description: Not all images are affected but enough are. Below is a screen shot of the issue with the image highlighted in nautilus to show that the color corruption seems to be eog rather than libjpeg. http://ubuntuone.com/1oFONmmTFXBzlHbM436Rwd ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: eog 3.3.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.92-0ubuntu1 Architecture: i386 CheckboxSubmission: ba9c4255a69726424c6447d1c48d6601 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Feb 22 09:13:48 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120201.1) SourcePackage: eog UpgradeStatus: Upgraded to precise on 2012-02-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1033253] Re: WebSphere Integration Developer 6.2 (Eclipse 3.4) - BPEL editor is slow for large windows
Problem still valid, I'm about to ugprade to 13.04 soon. So I will report if the bug will be still there (or more interestingly, whether the workaround would still work)...:-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrender in Ubuntu. https://bugs.launchpad.net/bugs/1033253 Title: WebSphere Integration Developer 6.2 (Eclipse 3.4) - BPEL editor is slow for large windows Status in “libxrender” package in Ubuntu: New Bug description: 1.) lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 2.) apt-cache policy libXrender1 libxrender1: Installed: 1:0.9.6-2build1 Candidate: 1:0.9.6-2build1 Version table: *** 1:0.9.6-2build1 0 500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy libXrender1:i386 libxrender1:i386: Installed: 1:0.9.6-2build1 Candidate: 1:0.9.6-2build1 Version table: *** 1:0.9.6-2build1 0 500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3.) What you expected to happen: Eclipse window rendering would be working at the similar speed as in Oneric. 4.) What happened instead: Eclipse was terribly slow. Conditions: WID 6.2 Linux version is 32-bit. Ubuntu 12.04 64-bit version installed with latest updates. ia32-libs and libstdc++5:i386 package to make WID 6.2 working. WID 6.2 was running smoothly on Ubuntu 11.10 (Oneiric) but that stopped directly after upgrade to Ubuntu 12.04. The problem is that window rendering (BPEL editor) started to be terribly slow (CPU at 100%). I tried to investigate the problem and finally after a few days and nights I've find out that the problem is in libXrender package. Since code has not been changed between the two Ubuntu releases, it's somehow related to how the package is build. 5.) My analysis of the problem: 5.1) Some simple tests first - Usage of different window environment had no effect (Unity, Gnome Shell, Gnome Classic, XFCE). - Usage of latest Xorg versions (xorg-edgers) had also no effect. - Usage of older/newer nvidia drivers had no effect. - Usage of xserver-xorg-video-noveau had no effect. 5.2) Compare versions and changelog http://lino.ubuntuupdates.org/pm/libxrender precisemainbase1:0.9.6-2build1 oneiricmainbase1:0.9.6-2 Change Log: Version: 1:0.9.6-2build12012-03-02 07:04:57 UTC libxrender (1:0.9.6-2build1) precise; urgency=low * No-change rebuild against current pkgbinarymangler to fix broken md5sums. (see LP #875466) -- Martin Pitt Wed, 29 Feb 2012 17:58:51 +0100 5.3) Locate file Precise: /usr/lib/i386-linux-gnu/libXrender.so.1.3.0 Oneiric: /usr/lib32/libXrender.so.1.3.0 5.4) Compare libXrender library dependency = By using ldd utility = nearly same output (ie.just addresses are different) 5.5) Filesize comparison (Result: Size differ significantly) Precise size: 34424 Oneiric size: 38520 5.6) Compare using file utility (Result: hashes are different) Precise: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0x62c06ccdf7ede559a439ac33ac35dec40f035a9c, stripped Oneiric: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0x05ad8f548663c542361448564b6f1c6f881f9e65, stripped 5.7) Compare libXrender path in loaded libraries (Result: path differs) Find all dynamic libraries lsof -p eclipse process | grep -E \.so\.|\.so | cut -c74- List library dependency (using ldd) for every loaded library Result: - Precise: All used libraries have following dependency: libXrender.so.1 = /usr/lib/i386-linux-gnu/libXrender.so.1 (0xf69bd000) - Oneiric: Not tested (already upgraded to Precise). Very likely /usr/lib32/libXrender.so.1. 5.8) libXrender is used by following loaded libraries /opt/IBM/WID62/configuration/org.eclipse.osgi/bundles/2282/1/.cp/libswt-atk-gtk-3453.so: /opt/IBM/WID62/configuration/org.eclipse.osgi/bundles/2282/1/.cp/libswt-cairo-gtk-3453.so: /opt/IBM/WID62/configuration/org.eclipse.osgi/bundles/2282/1/.cp/libswt-pi-gtk-3453.so: /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/engines/libclearlooks.so: /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/immodules/im-ibus.so: /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so: /usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/printbackends/libprintbackend-file.so: /usr/lib/i386-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so:
[Desktop-packages] [Bug 1113831] Re: Option to mark wireless connection as mobile to save costs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1113831 Title: Option to mark wireless connection as mobile to save costs Status in NetworkManager: Invalid Status in “network-manager” package in Ubuntu: Confirmed Status in “update-manager” package in Ubuntu: Confirmed Bug description: When on mobile broadband Ubuntu does not check for updates, which is a very good functionality. However, many people have data contracts on their smart phones and use tethering via WLAN to share the connection. The problem is that my phone appears as a hotspot and thus Ubuntu does not recognize that I am on broadband and uses most of my monthly traffic just to check for updates. I would strongly recommend a script in the WLAN configuration to mark a connection as mobile. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-3.7-generic 3.8.0-rc5 Uname: Linux 3.8.0-3-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Sat Feb 2 23:35:53 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-03-31 (308 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120331) IpRoute: default via 172.20.10.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.20.10.0/28 dev wlan0 proto kernel scope link src 172.20.10.3 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-01-23 (10 days ago) 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.7.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1113831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984785] Re: .goutputstream files polluting $HOME
IMHO making all Shutdown buttons in various *DEs work like Logout then shutdown can workaround or even fix many bugs including this one, especially for linux newbies. But it's a task of *DEs developers, not only Ubuntu/Unity ones. Excuse me if i'm spamming. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME Status in The G Library - GLib: Fix Released Status in Light Display Manager: New Status in X.Org X server: New Status in “glib2.0” package in Ubuntu: Fix Committed Status in “lightdm” package in Ubuntu: Invalid Status in “glib2.0” source package in Precise: Triaged Status in “lightdm” source package in Precise: Invalid Bug description: .goutputstream files polluting $HOME. Which software or operation is creating these and why? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xauth 1:1.0.6-1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ati ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Wed Apr 18 13:29:31 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xauth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 377322] Re: Nautilus sftp connection breaks spontaneously after a while, needing re-login to fix it
Sorry Murry I seemed to have misread your previous post. For some reason I though you were using precise. I have updated the ppa with a new Raring build based on my conversations with the upstream devs. Hopefully this one should do the trick. Please let me know how it goes. -- 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/377322 Title: Nautilus sftp connection breaks spontaneously after a while, needing re-login to fix it Status in GVFS: Confirmed Status in “gvfs” package in Ubuntu: Triaged Bug description: When I have used an sftp connection for a while - started from Places/Connect to Server or from a bookmark - it breaks, typically after an hour or so. The only way to get an sftp connection to that server again is to re login to my computer. The error message I get is Could not open location 'sftp://..' DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken Sometimes when this happens, my computer freezes for about 60 seconds. I have Ubuntu 9.04 64 bits - error happened on Hardy also - on a computer with an AMD64 processor. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/377322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170925] [NEW] System (ubuntu) freeze an start a loud beeping
Public bug reported: This problem happens in my Dell Inspirion 14 (Intel Pentium) when i change the monitor brightness too fast. When I do so, it freezes an start beeping (loud like hell). It also do this when i'm not using it, so it also crashes by itself. I don't know who (which program) is doing this. But I presume is some library that is not loaded, because while i was using preload it was never happened, but before an right after I removed preload it happen a lot. This is preload= http://sourceforge.net/projects/preload/ Thanks to all Luís HP Souza (more info) lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sat Apr 20 08:11:38 2013 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to quantal on 2013-02-18 (60 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug freeze i386 quantal running-unity ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1170925 Title: System (ubuntu) freeze an start a loud beeping Status in “xorg” package in Ubuntu: New Bug description: This problem happens in my Dell Inspirion 14 (Intel Pentium) when i change the monitor brightness too fast. When I do so, it freezes an start beeping (loud like hell). It also do this when i'm not using it, so it also crashes by itself. I don't know who (which program) is doing this. But I presume is some library that is not loaded, because while i was using preload it was never happened, but before an right after I removed preload it happen a lot. This is preload= http://sourceforge.net/projects/preload/ Thanks to all Luís HP Souza (more info) lsb_release -rd Description:Ubuntu 12.10 Release:12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sat Apr 20 08:11:38 2013 DistroCodename: quantal DistroVariant: ubuntu GpuHangFrequency: Several times a day MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to quantal on 2013-02-18 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1170925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170926] [NEW] Unable to have same song played more than once in a playlist
Public bug reported: I am creating a playlist for a tango-dancing event. It is custom to have a short song cortina between every 3rd or 4th song when changing dance style. I am unable to add the same cortina song more than once into each playlist (which I consider a bug - there is no mention of this in the documentation). So for a 3 hour event I need to use 18-20 different cortinas instead of perhaps 3-4 repeated some times. Procedure: 1.Select a song and drag it to the playlist or right click:add to playlist The song is added to the playlist. 2.Add some more songs. 3.Repeat step 1 for same song: The song is not appended to the playlist. This is however easily accomplished in Clementine player. If the playlist is created in Clementine and saved as .xspf file and loaded into Rhythmbox, same effect is realized: When a song appears more than once in the playlist is reached it is skipped from the list except for its first entry. Rhythmbox version:2.97-1ubuntu6.1 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1170926 Title: Unable to have same song played more than once in a playlist Status in “rhythmbox” package in Ubuntu: New Bug description: I am creating a playlist for a tango-dancing event. It is custom to have a short song cortina between every 3rd or 4th song when changing dance style. I am unable to add the same cortina song more than once into each playlist (which I consider a bug - there is no mention of this in the documentation). So for a 3 hour event I need to use 18-20 different cortinas instead of perhaps 3-4 repeated some times. Procedure: 1.Select a song and drag it to the playlist or right click:add to playlist The song is added to the playlist. 2.Add some more songs. 3.Repeat step 1 for same song: The song is not appended to the playlist. This is however easily accomplished in Clementine player. If the playlist is created in Clementine and saved as .xspf file and loaded into Rhythmbox, same effect is realized: When a song appears more than once in the playlist is reached it is skipped from the list except for its first entry. Rhythmbox version:2.97-1ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1170926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1158934] Re: HP ProBook 6570b using acpi_video0 for backlight rather than intel_backlight
This bug also affected at HP ProBook 4740s on kernel 3.8.0-raring -- 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/1158934 Title: HP ProBook 6570b using acpi_video0 for backlight rather than intel_backlight Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: When pressing the keys to increase or decrease backlight, or even using the Display dialog's slider, backlight doesn't change. However, the backlight level indicated by the prompt does change. The hardware in question is an HP ProBook 6570b laptop. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 22 19:31:40 2013 DistUpgraded: 2013-01-27 21:36:15,133 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: bcmwl, 6.20.155.1+bdcom, 3.8.0-12-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.8.0-13-generic, x86_64: installed virtualbox, 4.2.8, 3.8.0-12-generic, x86_64: installed virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17ab] InstallationDate: Installed on 2012-11-13 (129 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP ProBook 6570b MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=1a9c19c9-524c-47a2-89da-6dd88cb8f2ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to raring on 2013-01-27 (53 days ago) dmi.bios.date: 09/24/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICE Ver. F.31 dmi.board.name: 17AB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICEVer.F.31:bd09/24/2012:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1102:rvnHewlett-Packard:rn17AB:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6570b dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Fri Mar 22 19:28:05 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu3 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1158934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170926] Re: Unable to have same song played more than once in a playlist
This also applies to the Play Que, it is not possible to have same song in it more than once. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1170926 Title: Unable to have same song played more than once in a playlist Status in “rhythmbox” package in Ubuntu: New Bug description: I am creating a playlist for a tango-dancing event. It is custom to have a short song cortina between every 3rd or 4th song when changing dance style. I am unable to add the same cortina song more than once into each playlist (which I consider a bug - there is no mention of this in the documentation). So for a 3 hour event I need to use 18-20 different cortinas instead of perhaps 3-4 repeated some times. Procedure: 1.Select a song and drag it to the playlist or right click:add to playlist The song is added to the playlist. 2.Add some more songs. 3.Repeat step 1 for same song: The song is not appended to the playlist. This is however easily accomplished in Clementine player. If the playlist is created in Clementine and saved as .xspf file and loaded into Rhythmbox, same effect is realized: When a song appears more than once in the playlist is reached it is skipped from the list except for its first entry. Rhythmbox version:2.97-1ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1170926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097105] Re: PDF's are offset when printed with lpr, but not acroread
Hi After some investigations I found a relatively easy way to get arround this. The culprit beeing cups-filters. After downgrading it, evrything seemed OK. apt-cache policy cups-filters cups-filters: Installed: 1.0.18-0ubuntu0.1 Candidate:1.0.24-2ubuntu0.1 Versiontabel: 1.0.24-2ubuntu0.1 0 500 http://archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 1.0.24-2 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 *** 1.0.18-0ubuntu0.1 0 500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 How to downgrade? add the line deb http://archive.ubuntu.com/ubuntu/ precise-updates main to sources.list apt-get update apt-get install cups-filters=1.0.18-0ubuntu0.1 apt-mark hold cups-filters Hope this is useful Jack -- 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/1097105 Title: PDF's are offset when printed with lpr, but not acroread Status in “cups” package in Ubuntu: Confirmed Bug description: When printing pdf files from evince or lpr the result is a pdf file that is offset and usually cliped at the top and right edge. The following file was used www.opensource.apple.com/source/cups/cups-136/cups/test/testfile.pdf from evince select scalling as none select auto rotate and center the result is a printout that is shifted up and left so that hte lower and left edges can be seen the expected result is that all sides should be clipped given the testfile prints at the extreme boarders This only happens with 12.10. The printer works fine on 12.04 with the exact same drivers installed. These drivers are installed on both computers. The printer in question is a Brother DCP7065DN LPR driverdeb 2.1.0-1 35 KB 2011.Apr.01 cupswrapper driverdeb 2.0.4-2 13 KB 2011.Apr.01 downloaded from http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_prn.html#DCP-7065DN This test file can be printed as expected from acroread. The difference I believe is that evince and lpr pass along PDF and acroread passes postscript. this was observed by doing a file on the /var/spool/cups/d* This is also observed via libre office. when printing and one selects PDF for the 'printer language type' the offset is observed. if you select postscript from the 'printer language type' it prints as expected. I also have a MFC-J4510DW that prints perfectly from 12.10 all applications mentioned. Both printers have the latest firmware. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 7 20:44:47 2013 InstallationDate: Installed on 2012-07-01 (190 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lpstat: device for DCP7065DN: lpd://DCP/BINARY_P1 device for MFCJ4510DW: lpd://MFC/BINARY_P1 MachineType: Hewlett-Packard HP G72 Notebook PC MarkForUpload: True Papersize: letter PpdFiles: DCP7065DN: Brother DCP7065DN for CUPS MFCJ4510DW: Brother MFC-J4510DW CUPS ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=9bc8d282-ff75-4e67-b337-cf110d979925 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-12-23 (15 days ago) dmi.bios.date: 02/15/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1439 dmi.board.vendor: Hewlett-Packard dmi.board.version: 60.4F dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd02/15/2011:svnHewlett-Packard:pnHPG72NotebookPC:pvr058E11252710001620100:rvnHewlett-Packard:rn1439:rvr60.4F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP G72 Notebook PC dmi.product.version: 058E11252710001620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1097105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1072510] Re: Couldn't change keyring password
I can confirm this problem, too, on Mint 14 (Nadia) with Mate desktop 64Bit. The login keyring didn't exist, creating it has no effect. I had one called default, one named Vorgabe (which is a German term for default) and one without any name. When creating new keyrings (like new, or login), I can assign a password of free choice, but I won't be able to change these afterwards, producing the erorr message mentioned above. On the other hand I'm able to delete the keyrings completely, while a) you only see that deletion did take place after restarting seahorse b) the empty-name keyring stay even after deletion/restart and disappears after seconds attempt. I deleted all password keyrings (I know the PIN of my UMTS-SIM by mind, the other could only be for login), knowing I might possibly not be able to login. After logoff/logon (successfully with password prompt), I was not asked for a keyring password anymore! WLAN was connected immediately, and I was able to start the UMTS connection at once. I shut down my computer and rebooted, and as expected, no keyring prompt. So for me, this seems to be no problem anymore. In seahorse a new keyring with no name, unlocked and wihtout any stored passwords appeared. (Not sure, but I think it was already there after lo/li.) Context menu entry set as default (or how it is in English version) is greyed and can't be chosen, and the passwrod can't be changed (same error as m.a.). At the end there is only one point: why did I ever have to use a keyring? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1072510 Title: Couldn't change keyring password Status in “seahorse” package in Ubuntu: Confirmed Bug description: I have to double login into ubuntu and it's annoying to enter the same password twice. I'm trying to change the password or do anything but... Method ChangeWithPrompt with signature o on interface org.gnome.keyring.InternalUnsupportedGuiltRiddenInterface doesn't exist seahorse 3.6.2 http://i.imgur.com/ykHHV.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1072510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069064]
Thanks for help, I tried vga= but got message that it is deprecated. Using gfxpayload did helped a lot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1069064 Title: Screen keeps blinking after boot up Status in “xorg” package in Ubuntu: New Status in “xorg” package in openSUSE: In Progress Bug description: Hi, I tried installing ubuntu quantal on my acer 5002 laptop with sis card. But on boot from usb screen keeps flickering with only mouse pointer shows up on whole screen. I tried xubuntu as well and result is same. --- ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) Package: xorg 1:7.6+12ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30 Tags: precise ubuntu Uname: Linux 3.2.0-32-generic-pae i686 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069064]
I don't know, which resolution your panel needs. It might be possible to chose the right framebuffer mode. Try this # hwinfo --framebuffer Use the appropriate mode hexnumber (16bit mode recommended) as vga boot parameter. Example: Mode 0x0317: 1024x768 (+2048), 16 bits -- vga=0x317 To be honest: It's unlikely this ever been fixed. Nobody is still working on the sis driver upstream, the SiS company is no longer active in this area, and the driver is no longer building against the latest Xserver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1069064 Title: Screen keeps blinking after boot up Status in “xorg” package in Ubuntu: New Status in “xorg” package in openSUSE: In Progress Bug description: Hi, I tried installing ubuntu quantal on my acer 5002 laptop with sis card. But on boot from usb screen keeps flickering with only mouse pointer shows up on whole screen. I tried xubuntu as well and result is same. --- ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) Package: xorg 1:7.6+12ubuntu1 PackageArchitecture: i386 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30 Tags: precise ubuntu Uname: Linux 3.2.0-32-generic-pae i686 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1069064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170929] [NEW] Settings crashes (core dumped, no traceback) when getting bad schema
Public bug reported: $ python Python 2.7.4 (default, Apr 17 2013, 22:29:30) [GCC 4.7.3] on linux2 Type help, copyright, credits or license for more information. from gi.repository import Gio Gio.Settings.new(com.canonical.unity.panel) (process:2822): GLib-GIO-ERROR **: Settings schema 'com.canonical.unity.panel' is not installed Trace/breakpoint trap (core dumped) $ ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python-gi 3.8.0-2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sat Apr 20 08:49:34 2013 InstallationDate: Installed on 2013-02-16 (62 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True SourcePackage: pygobject UpgradeStatus: Upgraded to raring on 2013-04-19 (0 days ago) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1170929 Title: Settings crashes (core dumped, no traceback) when getting bad schema Status in “pygobject” package in Ubuntu: New Bug description: $ python Python 2.7.4 (default, Apr 17 2013, 22:29:30) [GCC 4.7.3] on linux2 Type help, copyright, credits or license for more information. from gi.repository import Gio Gio.Settings.new(com.canonical.unity.panel) (process:2822): GLib-GIO-ERROR **: Settings schema 'com.canonical.unity.panel' is not installed Trace/breakpoint trap (core dumped) $ ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python-gi 3.8.0-2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sat Apr 20 08:49:34 2013 InstallationDate: Installed on 2013-02-16 (62 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True SourcePackage: pygobject UpgradeStatus: Upgraded to raring on 2013-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1170929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170929] Re: Settings crashes (core dumped, no traceback) when getting bad schema
This is due to glib asserting when you try to access a nonexisting schema. This has been discussed many times and is indeed a bit ugly, but an upstream design decision. ** Package changed: pygobject (Ubuntu) = glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1170929 Title: Settings crashes (core dumped, no traceback) when getting bad schema Status in “glib2.0” package in Ubuntu: Won't Fix Bug description: $ python Python 2.7.4 (default, Apr 17 2013, 22:29:30) [GCC 4.7.3] on linux2 Type help, copyright, credits or license for more information. from gi.repository import Gio Gio.Settings.new(com.canonical.unity.panel) (process:2822): GLib-GIO-ERROR **: Settings schema 'com.canonical.unity.panel' is not installed Trace/breakpoint trap (core dumped) $ ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python-gi 3.8.0-2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sat Apr 20 08:49:34 2013 InstallationDate: Installed on 2013-02-16 (62 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MarkForUpload: True SourcePackage: pygobject UpgradeStatus: Upgraded to raring on 2013-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1170929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1161931] Re: Ubuntu 12.04 64Bit,X.org
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1161931 Title: Ubuntu 12.04 64Bit,X.org Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: The Error report says to me Acpi_OSC request failed (AE Error),Returned control mask:0x1d warning power/ level is deprecated; use power/control insstead ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39 Uname: Linux 3.2.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.64 Tue Oct 30 10:58:20 PDT 2012 GCC version: gcc-Version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Fri Mar 29 16:59:34 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current-updates, 304.64, 3.2.0-39-generic, x86_64: installed vboxhost, 4.2.10, 3.2.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need an easy workaround GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] JockeyStatus: firmware:dvb_usb - Firmware für DVB-Karten (Proprietär, Deaktiviert, Nicht benutzt) xorg:nvidia_current - Beschleunigter Grafiktreiber von NVIDIA (Proprietär, Deaktiviert, Nicht benutzt) xorg:nvidia_current_updates - Beschleunigter Grafiktreiber von NVIDIA (Nachträgliche Aktualisierungen) (Proprietär, Aktiviert, In Benutzung) xorg:nvidia_experimental_304 - Beschleunigter Grafiktreiber von NVIDIA (**Experimentell** Beta) (Proprietär, Deaktiviert, Nicht benutzt) xorg:nvidia_experimental_310 - Beschleunigter Grafiktreiber von NVIDIA (**Experimentell** Beta) (Proprietär, Deaktiviert, Nicht benutzt) MachineType: TOSHIBA SATELLITE P500 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-39-generic root=UUID=4ac388d0-abe8-4e68-8550-405723d38b5c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 12/15/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: 2.90 dmi.board.name: SATELLITE P500 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr2.90:bd12/15/2010:svnTOSHIBA:pnSATELLITEP500:pvrPSPGSE-00W00GGR:rvnTOSHIBA:rnSATELLITEP500:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: SATELLITE P500 dmi.product.version: PSPGSE-00W00GGR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1161931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1170933] [NEW] fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build
Public bug reported: wget http://www2.ati.com/drivers/linux/ati-driver- installer-11-12-x86.x86_64.run sudo sh ati-driver-installer-11-12-x86.x86_64.run --buildpkg Ubuntu/precise sudo dpkg -i fglrx*.deb And something crashed... ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.920-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40 Uname: Linux 3.2.0-40-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 DKMSKernelVersion: 3.2.0-40-generic-pae Date: Sat Apr 20 14:50:52 2013 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageVersion: 2:8.960-0ubuntu1.1 SourcePackage: fglrx-installer Title: fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1170933 Title: fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: wget http://www2.ati.com/drivers/linux/ati-driver- installer-11-12-x86.x86_64.run sudo sh ati-driver-installer-11-12-x86.x86_64.run --buildpkg Ubuntu/precise sudo dpkg -i fglrx*.deb And something crashed... ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.920-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40 Uname: Linux 3.2.0-40-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 DKMSKernelVersion: 3.2.0-40-generic-pae Date: Sat Apr 20 14:50:52 2013 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release i386 (20130213) MarkForUpload: True PackageVersion: 2:8.960-0ubuntu1.1 SourcePackage: fglrx-installer Title: fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1170933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1092933] [NEW] Two finger scrolling option disabled
You have been subscribed to a public bug: On my laptop with a synaptics touchpad, the option for two finger scrolling is grayed out, even though the touchpad/driver support it, as it can be enabled via the command line with synclient. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: scrolling -- Two finger scrolling option disabled https://bugs.launchpad.net/bugs/1092933 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170941] [NEW] Login dialog does not show username or password on first boot.
Public bug reported: On first boot after fresh install on Virtualbox, Raring RC does not show any user name or password fields in the login dialog (see attached screenshot). Clicking the down arrow makes them appear and they do show up normally on all subsequent restarts or logouts/logins. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sat Apr 20 09:13:13 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130420) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=xubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1274): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory ** (lightdm-gtk-greeter:1274): WARNING **: Failed to load user image: Failed to open file '/home/jack/.face': No such file or directory MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: Screenshot from 2013-04-20 09:10:19.png https://bugs.launchpad.net/bugs/1170941/+attachment/3649053/+files/Screenshot%20from%202013-04-20%2009%3A10%3A19.png -- 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/1170941 Title: Login dialog does not show username or password on first boot. Status in “lightdm” package in Ubuntu: New Bug description: On first boot after fresh install on Virtualbox, Raring RC does not show any user name or password fields in the login dialog (see attached screenshot). Clicking the down arrow makes them appear and they do show up normally on all subsequent restarts or logouts/logins. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sat Apr 20 09:13:13 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130420) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=xubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1274): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory ** (lightdm-gtk-greeter:1274): WARNING **: Failed to load user image: Failed to open file '/home/jack/.face': No such file or directory MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1170941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1092933] Re: Two finger scrolling option disabled
This panel comes from GNOME Control Center. Retargeting accordingly. ** Project changed: switchboard = gnome-control-center (Ubuntu) -- 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/1092933 Title: Two finger scrolling option disabled Status in “gnome-control-center” package in Ubuntu: New Bug description: On my laptop with a synaptics touchpad, the option for two finger scrolling is grayed out, even though the touchpad/driver support it, as it can be enabled via the command line with synclient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1092933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 597825]
This is shown on Australis mockups. Need to know if it's part of the specs or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/597825 Title: Menu accelerators in Firefox don't follow the GNOME policy. Status in The Mozilla Firefox Browser: Confirmed Status in One Hundred Paper Cuts: Fix Released Status in “firefox” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Won't Fix Status in “openoffice.org” package in Ubuntu: Invalid Bug description: Binary package hint: firefox The current GNOME default is that menu accelerators are hidden, and shown when you press the ALT key. Firefox doesn't observe this policy and have their menu accelerators displayed all the time. Also, pressing ALT alone in GNOME and Firefox doesn't invoke any menu command. This inconsistent behavior is a usability issue and also makes Ubuntu desktop look unprofessional. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Wed Jun 23 21:37:05 2010 EcryptfsInUse: Yes FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A ProcEnviron: PATH=(custom, user) LANG=pl_PL.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/597825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170941] Re: Login dialog does not show username or password on first boot.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1170941 ** Tags added: iso-testing -- 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/1170941 Title: Login dialog does not show username or password on first boot. Status in “lightdm” package in Ubuntu: New Bug description: On first boot after fresh install on Virtualbox, Raring RC does not show any user name or password fields in the login dialog (see attached screenshot). Clicking the down arrow makes them appear and they do show up normally on all subsequent restarts or logouts/logins. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sat Apr 20 09:13:13 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release i386 (20130420) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter user-session=xubuntu LightdmGreeterLog: ** (lightdm-gtk-greeter:1274): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory ** (lightdm-gtk-greeter:1274): WARNING **: Failed to load user image: Failed to open file '/home/jack/.face': No such file or directory MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1170941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 871985] Re: The printing panel shouldn't display errors about firewalld not running
** Changed in: elementaryos Importance: Undecided = High -- 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/871985 Title: The printing panel shouldn't display errors about firewalld not running Status in elementary OS: Triaged Status in GNOME Control Center: Fix Released Status in The Linux Mint Distribution: New Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: WORKAROUND: As an alternative to the printer configuration tool from the new Gnome Shell control center, you can still use system-config- printer. To open it, just press Alt+F2, type system-config-printer and press Enter. It appears a patch was added to Gnome back in July that requires FirewallD to be running in order to add a network printer. see: http://mail.gnome.org/archives/commits-list/2011-July/msg09761.html This only appears to affect those using the Gnome 3 desktop environment, and this problem is not present in Unity, so you can still add the pinter in Unity's control panel, but users wanting to use Gnome will encounter this. The specific error message is: FirewallD is not running. Network printer detection needs services mdns, ipp, ipp-client and samba-client enabled on firewall. The documentation in the mentioned patch suggests this behavior is actually intentional. However, FirewallD is, as far as I know, specific to Fedora. 1) release: Ubuntu Oneiric Beta 2 (64 bit, but others likely to be affected) 2) issue is more specific to the Gnome 3 desktop environment as a whole, although there may be individual packages that can be patched to circumvent this behavior 3) I expected the previous behavior of being able to add a network printer without having a package that does not even exist for Ubuntu 4) I got this nice error message that tells me FirewallD is not running. Network printer detection needs services mdns, ipp, ipp- client and samba-client enabled on firewall. As far as a solution goes, a documented work-around may be a good idea (such as an FAQ entry that says simply to install the network printer in Unity), at least until a more permanent solution can be found. This is bug was originally asked as a question here: https://answers.launchpad.net/ubuntu/+source/gnome- nettool/+question/173836 but it was suggested that a bug report be submitted instead. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 10 14:49:32 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu1 indicator-datetime 0.3.0-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/871985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170832] Re: Facebook Requires Authorization when already authorized
Found what causes this. It only seems to happen if I have pidgin open and signed into facebook on my other computer. I don't know why empathy can't handle signing into facebook while pidgin is connected to it, I've never had this problem with pidgin or any other in client not being able to sign in when its signed in on another computer... I switched to trillian on that computer and empathy seems to like that better and I haven't seen the problem so far. -- 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/1170832 Title: Facebook Requires Authorization when already authorized Status in “empathy” package in Ubuntu: New Bug description: I am running fully updated 13.04 64-bit. I simply cannot get empathy/UOA to connect to facebook. When I add the account in UOA everything seems to go well, facebook login page loads, it logs in successfully, facebook recognizes the session as safari on linux; but upon completing the setup in UOA empathy refuses to connect to it and keeps telling me it requires authorization. I've Tried the following: Removing the account from UOA Ending all active sessions on facebook and deleting the ubuntu app rebooting adding account in UOA, and allowing the ubuntu app to manage my messages etc... Didn't help at all. pidgin connects fine on the same computer. Sometimes it does let me add it and it works for a while, but eventually this issue happens again and leaves me totally unable to successfully add a facebook account for quite some time, until it randomly decides it wants to work again. Empathy/UOA in 13.04 has been unreliable to the point of ridiculousness, the application is basically unusable and can't handle the one basic task of an instant messaging program, which is connecting to my accounts reliably. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 19 16:57:50 2013 InstallationDate: Installed on 2013-04-17 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130416) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1170832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170949] [NEW] AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
Public bug reported: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) ** Affects: libffado (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jackd libffado quantal ** Attachment added: connection.png https://bugs.launchpad.net/bugs/1170949/+attachment/3649069/+files/connection.png ** Attachment removed: connection.png https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649069/+files/connection.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** Attachment added: control.mid https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649073/+files/control.mid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** Attachment added: result_44100.log https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649074/+files/result_44100.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** Attachment added: result_96000_1.log https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649077/+files/result_96000_1.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** Attachment added: result_96000_2.log https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649078/+files/result_96000_2.log ** Description changed: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. - Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. - amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. + Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. + amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. - See connection.png. + See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. - I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. - The captured data is converted to text data, result_.log. + I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. + The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. + + This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) ** Summary changed: - MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz + AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** Attachment added: result_88200.log https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649076/+files/result_88200.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** Attachment added: connection.png https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649072/+files/connection.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** Attachment added: result_48000.log https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649075/+files/result_48000.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libffado in Ubuntu. https://bugs.launchpad.net/bugs/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz Status in “libffado” package in Ubuntu: New Bug description: I confirm this bug with my AudioFirePre8. I generate this bug in the way below: 1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with snd-usb-audio.ko (ALSA). 2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU 0404 USB 3.Prepare reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170963] [NEW] Edit Connections doesn't give focus to window if already open
Public bug reported: Steps to reproduce: 1. In the nm-applet menu, select Edit Connections. The Network Connections window opens. 2. Leave it open and do other stuff, e.g. use other applications, so the Network Connections window remains in the background 3. Repeat step 1 Expected behavior: the Network Connections window should get focus and come to front Observed behavior: nothing happens. You are left wondering why on earth the Edit Connections option doesn't work. Until you figure out the window is already open. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sat Apr 20 16:08:42 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-06-23 (1032 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 77.210.136.75 169.254.0.0/16 dev ppp0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2013-01-13 (97 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-08-30T13:38:55.126319 nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB0gsm connected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless disconnected /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.6.0connected enabled enabled enabledenabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- 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/1170963 Title: Edit Connections doesn't give focus to window if already open Status in “network-manager” package in Ubuntu: New Bug description: Steps to reproduce: 1. In the nm-applet menu, select Edit Connections. The Network Connections window opens. 2. Leave it open and do other stuff, e.g. use other applications, so the Network Connections window remains in the background 3. Repeat step 1 Expected behavior: the Network Connections window should get focus and come to front Observed behavior: nothing happens. You are left wondering why on earth the Edit Connections option doesn't work. Until you figure out the window is already open. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sat Apr 20 16:08:42 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-06-23 (1032 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IpRoute: default via 10.64.64.64 dev ppp0 proto static 10.64.64.64 dev ppp0 proto kernel scope link src 77.210.136.75 169.254.0.0/16 dev ppp0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to quantal on 2013-01-13 (97 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-08-30T13:38:55.126319 nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB0gsm connected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless disconnected /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.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1170952] Re: icons not added to launcher
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1170952 ** Tags added: iso-testing -- 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/1170952 Title: icons not added to launcher Status in “software-center” package in Ubuntu: New Bug description: Hallo Not sure if this is a software-center or unity bug. When I installa new application via software-center, it is no more automatically added to the launcher, is this a new behavior ? Thanks Fabio ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: software-center 5.6.0-0ubuntu2 Uname: Linux 3.9.0-030900rc3-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 16:14:04 2013 InstallationDate: Installed on 2013-02-22 (56 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130222) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.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/ubuntu/+source/software-center/+bug/1170952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1168464] Re: I can not hear any sound from Samsung Chronos 7 - NP700Z5C-S01TR's right internal speaker if I shut down Windows then log in to Ubuntu.
** Attachment added: alsa-info.sh https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1168464/+attachment/3649169/+files/alsa-info.sh -- 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/1168464 Title: I can not hear any sound from Samsung Chronos 7 - NP700Z5C-S01TR's right internal speaker if I shut down Windows then log in to Ubuntu. Status in “alsa-driver” package in Ubuntu: New Bug description: Steps to produce: 1- Log in to Windows 2- Shutdown Windows 3- Log in to Ubuntu Temporary solution: 1- Suspend Ubuntu 2- Log in Ubuntu or 1- Shutdown Ubuntu 2- Re-log in to Ubuntu ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 2286 F pulseaudio Date: Fri Apr 12 18:34:38 2013 InstallationDate: Installed on 2013-03-28 (15 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 2286 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [700Z3C/700Z5C, Realtek ALC269VC, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04AAG 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.:bvrP04AAG:bd11/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3C/700Z5C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 700Z3C/700Z5C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-04-05T22:53:31.618392 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1168464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 401483] Re: the party mode doesn't allow to double click on a song
this bug is still present in 2013. kubuntu raring Thank you ** Changed in: rhythmbox (Ubuntu) Status: Triaged = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/401483 Title: the party mode doesn't allow to double click on a song Status in The Rhythmbox Music Management Application: Confirmed Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: I have an Acer Aspire One running Ubuntu 9.04 desktop, and because of the small screen I often run application in fullscreen. I noticed that in fullscreen Rythmbox you cannot click on a song to play it, it will continue the playing song and display Not Playing. When i go back to normal mode everythings fine. The version of Rhythmbox is 0.12.0. Jim To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/401483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 401483] Re: the party mode doesn't allow to double click on a song
actually not a bug in rhythmbox 2.98 - it is added to queue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/401483 Title: the party mode doesn't allow to double click on a song Status in The Rhythmbox Music Management Application: Confirmed Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: I have an Acer Aspire One running Ubuntu 9.04 desktop, and because of the small screen I often run application in fullscreen. I noticed that in fullscreen Rythmbox you cannot click on a song to play it, it will continue the playing song and display Not Playing. When i go back to normal mode everythings fine. The version of Rhythmbox is 0.12.0. Jim To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/401483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1158934] Re: HP ProBook 6570b using acpi_video0 for backlight rather than intel_backlight
As a reminder acpi_video should always be a more appropriate controller than intel_backlight. That it appears not to be is either a bug in the acpi firmware or the acpi driver for your system. -- 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/1158934 Title: HP ProBook 6570b using acpi_video0 for backlight rather than intel_backlight Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: When pressing the keys to increase or decrease backlight, or even using the Display dialog's slider, backlight doesn't change. However, the backlight level indicated by the prompt does change. The hardware in question is an HP ProBook 6570b laptop. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 22 19:31:40 2013 DistUpgraded: 2013-01-27 21:36:15,133 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: bcmwl, 6.20.155.1+bdcom, 3.8.0-12-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.8.0-13-generic, x86_64: installed virtualbox, 4.2.8, 3.8.0-12-generic, x86_64: installed virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17ab] InstallationDate: Installed on 2012-11-13 (129 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP ProBook 6570b MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=1a9c19c9-524c-47a2-89da-6dd88cb8f2ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to raring on 2013-01-27 (53 days ago) dmi.bios.date: 09/24/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICE Ver. F.31 dmi.board.name: 17AB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICEVer.F.31:bd09/24/2012:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1102:rvnHewlett-Packard:rn17AB:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6570b dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Fri Mar 22 19:28:05 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu3 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1158934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170971] [NEW] Start laptop and login screen doesn't appear
Public bug reported: This seems to occur randomly. Upon Restarting or starting my laptop when it reaches the point of logging in (or when the sound of the boot finishing with the drums occurs) I will sometimes be greeted with a blank black screen with my cursor also present. I can then pres ctrl + alt + F1 stop lightdm and then start it once again and then procede to log in and use the laptop as I normally would. Release final beta of 13.04 (NOT a daily release) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 12:16:47 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1170971 Title: Start laptop and login screen doesn't appear Status in “lightdm” package in Ubuntu: New Bug description: This seems to occur randomly. Upon Restarting or starting my laptop when it reaches the point of logging in (or when the sound of the boot finishing with the drums occurs) I will sometimes be greeted with a blank black screen with my cursor also present. I can then pres ctrl + alt + F1 stop lightdm and then start it once again and then procede to log in and use the laptop as I normally would. Release final beta of 13.04 (NOT a daily release) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 12:16:47 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1170971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170977] [NEW] [K53SD, Realtek ALC269VB, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: I fixed the glitches with load-module module-udev-detect tsched=0 and load-module module-udev-detect tsched=0 like I read on https://wiki.ubuntu.com/Audio/PositionReporting. I had to apply both fixes to solve the problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 18:52:06 2013 InstallationDate: Installed on 2012-10-23 (178 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [K53SD, Realtek ALC269VB, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to raring on 2013-03-06 (44 days ago) dmi.bios.date: 11/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SD.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SD.202:bd11/02/2011:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1170977 Title: [K53SD, Realtek ALC269VB, Speaker, Internal] Underruns, dropouts or crackling sound Status in “alsa-driver” package in Ubuntu: New Bug description: I fixed the glitches with load-module module-udev-detect tsched=0 and load-module module-udev-detect tsched=0 like I read on https://wiki.ubuntu.com/Audio/PositionReporting. I had to apply both fixes to solve the problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 18:52:06 2013 InstallationDate: Installed on 2012-10-23 (178 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or crackling sound Title: [K53SD, Realtek ALC269VB, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to raring on 2013-03-06 (44 days ago) dmi.bios.date: 11/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53SD.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SD.202:bd11/02/2011:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1170977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170976] [NEW] Desktop icons changed by user, display white border around them
Public bug reported: Right click on a desktop icon and select properties. Select a new icon via user/share/icons. The new icon then displays a white border. This is happening with my mounted usb thumb drives and a usb hard drive. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 17:53:01 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1011x738+159+129' InstallationDate: Installed on 2013-04-13 (7 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130413) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages ** Summary changed: - Desktop icons changed by user display white border arounf them + Desktop icons changed by user display white border around them ** Summary changed: - Desktop icons changed by user display white border around them + Desktop icons changed by user, display white border around them -- 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/1170976 Title: Desktop icons changed by user, display white border around them Status in “nautilus” package in Ubuntu: New Bug description: Right click on a desktop icon and select properties. Select a new icon via user/share/icons. The new icon then displays a white border. This is happening with my mounted usb thumb drives and a usb hard drive. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 17:53:01 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1011x738+159+129' InstallationDate: Installed on 2013-04-13 (7 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130413) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1170976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1012277] Re: Closing laptop lid should not blank external monitor
Alezandr tricks worked! It would still be great to have a proper fix implemented eventually :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1012277 Title: Closing laptop lid should not blank external monitor Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: I'm using Precise Pangolin installed from scratch, with the latest updates. txelu@txelu-acer:~$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 My problem is that I have my laptop connected to an external monitor, and if I started Ubuntu with the lid open I can't close, because not only the laptop screen goes blank, but also the external monitor. As a curious detail if I close the lid right after switching on the laptop, before Ubuntu starts up, it works as expected. Of course, I have set the Energy configuration to do nothing on closing the lid, and I agree that the laptop screen in that situation should go black, but not the external screen. There is a similar bug filled against previous versions of Ubuntu (#416236) that was considered a regression, but in that case there was a workaround using gconf-editor to manually edit the settings for the gnome-power-manager, but there is no such a entry now in 12.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1012277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063965] Re: Choppy sound in 12.10
lspci -v | grep -A7 -i audio 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) Subsystem: Packard Bell B.V. Device c017 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at ac34 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel Lubuntu 12.10 32bits Not sound, only choppy sound at start up. -- 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/1063965 Title: Choppy sound in 12.10 Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Distro:- Ubuntu 12.10 Quantal, What I suspect is that sound is muted and turned on at a fast pace and that gives it the choppy sound. I discovered that If I choose Sound Card ;- Mixer - HDA Intel - the surround sliders show mute/on at a fast rate, with - do - Mixer - Play back: Build in Audio Analog Stereo - the master sliders jumps up and down rapidly a short distance. I find the same happening on U tube. Movie Player with videos not so badly affected. Following is reports that I thought could help to pin point problem. If more info needed, I would gladly provide such. Still new at this so please bear with me. Thanks in advance for help that I know would be forthcoming. ~$ lspci -v | grep -A7 -i audio 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01) Subsystem: Foxconn International, Inc. Device 0dc2 Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at f9ffc000 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel Kernel modules: snd-hda-intel sudo aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 1: ALC662 rev1 Digital [ALC662 rev1 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 lspci 00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03) 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 01) 00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01) 00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01) 00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01) 00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01) 00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 01) 00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 01) 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce 8500 GT] (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1063965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 611796] Re: Incorrect detect and playback of TrueHD audio
** Changed in: gstreamer Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/611796 Title: Incorrect detect and playback of TrueHD audio Status in The GStreamer Multimedia Framework: Invalid Status in “gstreamer0.10” package in Ubuntu: Triaged Bug description: GStreamer can playback ac3 part of TrueHD audio track, but TrueHD without ac3 - can't. Also GStreamer incorrect detect TrueHD like audio/x-unknown. It's strange because ffmpeg support TrueHD. Sample of TrueHD with ac3: http://sharebee.com/b4081752 GStreamer playback ac3 part of TrueHD. Samples of TrueHD without ac3: http://sharebee.com/a3397697 http://sharebee.com/b4fe9bbf GStream can't playback it with sound. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgstreamer0.10-0 0.10.30-1 ProcVersionSignature: Ubuntu 2.6.35-11.16-generic 2.6.35-rc5 Uname: Linux 2.6.35-11-generic x86_64 Architecture: amd64 Date: Sat Jul 31 00:03:50 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/611796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170984] [NEW] display background not able to change
Public bug reported: In my ubuntu 13.04 desktop background remains in white.It remains white even if wallpaper is changed , but icons and side menu bar colour remains default.it happened when i updated using sytem update.All other things are working well.Please help me, i dont have much technical knowledge.i have also installed kubuntu plasma desktopLnetbook package,while running kubuntu there is no problem,above mentioned problem is only when i run gnome versions or ubuntu ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 20 21:20:45 2013 DistUpgraded: 2013-04-12 16:47:13,637 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c652] MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=C098C74B98C73F22 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to raring on 2013-04-12 (8 days ago) dmi.bios.date: 06/14/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P04RAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP300E5X-S01AE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04RAC:bd06/14/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4C/300E5C/300E7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5X-S01AE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E4C/300E5C/300E7C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 20 21:19:32 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1170984 Title: display background not able to change Status in “xorg” package in Ubuntu: New Bug description: In my ubuntu 13.04 desktop background remains in white.It remains white even if wallpaper is changed , but icons and side menu bar colour remains default.it happened when i updated using sytem update.All other things are working well.Please help me, i dont have much technical knowledge.i have also installed kubuntu plasma desktopLnetbook package,while running kubuntu there is no problem,above mentioned problem is only when i run gnome versions or ubuntu ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 20 21:20:45 2013 DistUpgraded:
[Desktop-packages] [Bug 1169333] Re: Screen resolution too low and missing launcher when connected to HDTV via HDMI
** Package changed: xserver-xorg-video-openchrome (Ubuntu) = xserver- xorg-video-ati (Ubuntu) ** Changed in: xserver-xorg-video-ati (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1169333 Title: Screen resolution too low and missing launcher when connected to HDTV via HDMI Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: I just unplugged my HDMI cable which was connected to the HDTV and the resolution was restored to its highest without my doing anything and the Launcher reappeared. Time for more experimentation. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Mon Apr 15 16:46:00 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, x86_64: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-27-generic, x86_64: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3949] InstallationDate: Installed on 2013-04-10 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: LENOVO 4311 MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=unknown PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-28-generic root=UUID=6f183dc9-9025-4214-9c39-d514db59f494 ro quiet splash radeon.audio=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 36CN19WW(V2.05) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Guam dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr36CN19WW(V2.05):bd09/07/2010:svnLENOVO:pn4311:pvrIdeaPadZ565:rvnLENOVO:rnGuam:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 4311 dmi.product.version: IdeaPad Z565 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1169333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170986] [NEW] Unity effects are slow
Public bug reported: All Unity effects run slow on my computer (Ati Radeon X1600 256 MB DDR3, Intel Core 2 Duo 2 GHz). The Dash opens slow, the Unity window switcher is very slow, too. I can say that all effects are to some extent slow and making the system slow. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-radeon 1:7.1.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 20 20:41:49 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV530/M56-P [Mobility Radeon X1600] [1002:71c5] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Compaq nx9420 Notebook [103c:309f] InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130420) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=UUID=41d9ada4-0b3e-4eda-a39d-989b1a33d502 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YAF Ver. F.1D dmi.board.name: 309F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 54.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YAFVer.F.1D:bd07/11/2008:svnHewlett-Packard:pn:pvrF.1D:rvnHewlett-Packard:rn309F:rvrKBCVersion54.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.1D dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 20 16:42:51 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 raring third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1170986 Title: Unity effects are slow Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: All Unity effects run slow on my computer (Ati Radeon X1600 256 MB DDR3, Intel Core 2 Duo 2 GHz). The Dash opens slow, the Unity window switcher is very slow, too. I can say that all effects are to some extent slow and making the system slow. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-radeon 1:7.1.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Apr 20 20:41:49 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV530/M56-P [Mobility Radeon X1600] [1002:71c5] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Compaq nx9420 Notebook [103c:309f] InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130420) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=UUID=41d9ada4-0b3e-4eda-a39d-989b1a33d502 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install
[Desktop-packages] [Bug 1159398] Re: buggy openchrome driver renders desktop unusable
Hi Kyle. Could you please attach the photo of the monitor's screen? It will be very useful in resolve problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1159398 Title: buggy openchrome driver renders desktop unusable Status in “xserver-xorg-video-openchrome” package in Ubuntu: Confirmed Bug description: I'm having a serious graphics problem in Ubuntu 13.04. When the X starts up, I get a glitchy set of squares that turns red with a discolored overlay of what I should be seeing. I also see no cursor whatsoever. Using lspci I got this for my video card: 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) Additional Details: Openchrome has worked perfectly up until this release of Ubuntu 13.04 and assuming latest release of openchrome. What I am guessing is my video card is having problems with GLX, though there doesn't seem to be any easy way to disable it (which is something I shouldn't have to do in the first place). The little bit of what you're *supposed* to see is also updating at an unnervingly low framerate, furthing my suspicion that it's a serious problem with acceleration. It takes a while for the (glitchy) display to appear in the first place. It didn't (thankfully) keep me from switching consoles. The boot splash is show in text-mode only (this specific anomaly has happed in previous releases though strangly on on the live session) Please see if you can fix this or forward this to someone who can see what they can do. Thank you for reading my bug request. --- .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu2 Architecture: i386 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu GraphicsCard: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] [1106:3344] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Gateway, Inc. Device [107b:0216] LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130321) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gateway MX3215 MarkForUpload: True Package: xserver-xorg-video-openchrome 1:0.3.1-0ubuntu1 PackageArchitecture: i386 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Tags: raring ubuntu single-occurrence reproducible Uname: Linux 3.8.0-13-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: XorgConf: Section Device Identifier VIA Unichrome Pro Driver vesa EndSection dmi.bios.date: 02/22/2006 dmi.bios.vendor: Phoenix dmi.bios.version: 73.07 dmi.board.vendor: Gateway dmi.board.version: Rev1.73.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvr73.07:bd02/22/2006:svnGateway:pnMX3215:pvr73.07:rvnGateway:rn:rvrRev1.73.07:cvnGateway:ct8:cvrN/A: dmi.product.name: MX3215 dmi.product.version: 73.07 dmi.sys.vendor: Gateway version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Sun Mar 24 21:55:00 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu2b1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1170989] [NEW] Facebook account not added to accounts after authorization
Public bug reported: 12.04.2 fresh install and fully updated. When configuring gwibber accounts Twitter is added to the accounts pane after completing authorization. When configuring Facebook account the authorization dialog shows up but when completed the authorization dialog closes but the account is not added to the configured accounts pane neither gwibber shows any content from facebook account. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gwibber 3.4.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.5.0-27.46~precise1-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 Date: Sat Apr 20 18:49:56 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwibber (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1170989 Title: Facebook account not added to accounts after authorization Status in “gwibber” package in Ubuntu: New Bug description: 12.04.2 fresh install and fully updated. When configuring gwibber accounts Twitter is added to the accounts pane after completing authorization. When configuring Facebook account the authorization dialog shows up but when completed the authorization dialog closes but the account is not added to the configured accounts pane neither gwibber shows any content from facebook account. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gwibber 3.4.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.5.0-27.46~precise1-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 Date: Sat Apr 20 18:49:56 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1170989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170987] [NEW] xscreensaver activates after logging in
Public bug reported: Under certain conditions, Xscreensaver activates after a regular login thus requiring login credentials a second time in Lubuntu. When I switch users in LXDE and then log out of the second user I get the login screen, as expected. Then when I enter the login credentials for the first user, the next thing I am greeted with is Xscreensaver's login. So I actually need to log in twice, in two different ways, to get back to the original session. This happens even if I am only out of the original user's desktop for a few seconds. I would expect that the login screen should get me fully back to my original desktop without needing to enter the password a second time at the Xscreensaver. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xscreensaver 5.15-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 20:45:49 2013 InstallationDate: Installed on 2013-03-09 (42 days ago) InstallationMedia: Lubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130308) MarkForUpload: True SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xscreensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1170987 Title: xscreensaver activates after logging in Status in “xscreensaver” package in Ubuntu: New Bug description: Under certain conditions, Xscreensaver activates after a regular login thus requiring login credentials a second time in Lubuntu. When I switch users in LXDE and then log out of the second user I get the login screen, as expected. Then when I enter the login credentials for the first user, the next thing I am greeted with is Xscreensaver's login. So I actually need to log in twice, in two different ways, to get back to the original session. This happens even if I am only out of the original user's desktop for a few seconds. I would expect that the login screen should get me fully back to my original desktop without needing to enter the password a second time at the Xscreensaver. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xscreensaver 5.15-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 20:45:49 2013 InstallationDate: Installed on 2013-03-09 (42 days ago) InstallationMedia: Lubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130308) MarkForUpload: True SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1170987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1169333] Re: Screen resolution too low and missing launcher when connected to HDTV via HDMI
Additional information. On both Quantal and Raring, the output on the HDTV is about 5% larger than the laptop display. I can just get to the lower half of the panel and about half the launcher. Watching streaming videos is a bit hard as a result as some controls are barely visible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1169333 Title: Screen resolution too low and missing launcher when connected to HDTV via HDMI Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: I just unplugged my HDMI cable which was connected to the HDTV and the resolution was restored to its highest without my doing anything and the Launcher reappeared. Time for more experimentation. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Mon Apr 15 16:46:00 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, x86_64: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-27-generic, x86_64: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3949] InstallationDate: Installed on 2013-04-10 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: LENOVO 4311 MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en TERM=unknown PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-28-generic root=UUID=6f183dc9-9025-4214-9c39-d514db59f494 ro quiet splash radeon.audio=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 36CN19WW(V2.05) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Guam dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr36CN19WW(V2.05):bd09/07/2010:svnLENOVO:pn4311:pvrIdeaPadZ565:rvnLENOVO:rnGuam:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 4311 dmi.product.version: IdeaPad Z565 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1169333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170987] Re: xscreensaver activates after logging in
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xscreensaver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1170987 Title: xscreensaver activates after logging in Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Under certain conditions, Xscreensaver activates after a regular login thus requiring login credentials a second time in Lubuntu. When I switch users in LXDE and then log out of the second user I get the login screen, as expected. Then when I enter the login credentials for the first user, the next thing I am greeted with is Xscreensaver's login. So I actually need to log in twice, in two different ways, to get back to the original session. This happens even if I am only out of the original user's desktop for a few seconds. I would expect that the login screen should get me fully back to my original desktop without needing to enter the password a second time at the Xscreensaver. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xscreensaver 5.15-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 20:45:49 2013 InstallationDate: Installed on 2013-03-09 (42 days ago) InstallationMedia: Lubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130308) MarkForUpload: True SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1170987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080102] Re: unity launcher drawing almost completely blank
*** This bug is a duplicate of bug 806248 *** https://bugs.launchpad.net/bugs/806248 I have observed this bug to happen around the 25th day of uptime, so I believe it to be the same bug as Bug #806248, unity::TimeUtil::TimeDelta returns an int value which overflows after 24 days of uptime. I have found a workaround less horrible than a reboot: the shell command: sudo service lightdm restart which allows the auto-login to operate again, so a remote vnc access can be re-established. ** This bug has been marked a duplicate of bug 806248 unity::TimeUtil::TimeDelta returns an int value which overflows after 24 days of uptime -- 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/1080102 Title: unity launcher drawing almost completely blank Status in “unity” package in Ubuntu: New Bug description: Each time this bug has cropped up, the session has been running for quite a while. I run an interactive session via VNC, as as such the auto-hide for the launcher must be turned off. At some point, the left-side launcher rectangle gets repeatedly drawn while interacting with applications (the mouse is not positioned within the launcher rectangle as this happens), and soon after, the left-side launcher rectangle appears almost completely blank (only highlighted background drawn there), with just the barest hint of what appears to be launcher icon partially visible at the top. Running unity --reset does not restore the launcher. Attempting to log-out and log-in again doesn't work because auto-log-in doesn't auto-log-in after a log-out. In this state the launcher cannot be operated to start additional applications or restore visibility of minimized windows. The only recovery I've been able to perform is a system reboot. This bug is made worse by three other longstanding problems: 1) Auto-hide of the launcher is broken under VNC, and 2) auto-log-in doesn't operate after a log-out, and 3) vino-server doesn't start until log-in/auto-log-in. I'll try to submit these as additional bugs A screen-shot exhibiting the sorry state of the display when the bug occurs is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1080102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1138251] Re: Desktop wallpaper Colors Gradients will not change color
install dconf-tools run 'dconf-editor' select org.gnome.desktop.background run gnome-control-center, select background color. dconf Editor immediately show changed values : Name: primary-color Value:rgb(138,226,52) Type: String Default: '#023c88' Name: secondary-color Value: rgb(206,92,0) Type: String Default: '#5789ca' default color value is '#RRGGBB' style, but gnome-control-center set 'rgb(dd,dd,dd)' style. close gnome-control-center, set '#RRGGBB' manually via dconf-editor, then Desktop background color change successfully. -- 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/1138251 Title: Desktop wallpaper Colors Gradients will not change color Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce - System Settings - Appearances - Background Colors Gradients - Set a new sold color What happens - Background remains black. This is the same for solid colors and gradients What should happen - Background should change to new color ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 1 17:43:58 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] InstallationDate: Installed on 2013-02-11 (18 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210) MachineType: Dell Inc. Dell System XPS 15Z MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-8-generic root=UUID=93acc5a7-d531-4af3-a215-472a7bd065d6 ro acpi_backlight=vendor dell_laptop.backlight=0 quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 060G42 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.:bvrA04:bd07/27/2011:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS 15Z dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.03.01-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1138251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170987] Re: xscreensaver activates after logging in
This bug affects me as well, but the actions triggering it are different, in my case. I have several different partitions on my machine, and whenever I boot one of the other partitions, the next time I boot the Lubuntu partition (LXDE), immediately after logging-in (and after the desktop appears), XScreensaver activates, and I have to re-enter my password into XScreensaver, after which the desktop re-appears, and everything is fine. I am using Lubuntu 12.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1170987 Title: xscreensaver activates after logging in Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Under certain conditions, Xscreensaver activates after a regular login thus requiring login credentials a second time in Lubuntu. When I switch users in LXDE and then log out of the second user I get the login screen, as expected. Then when I enter the login credentials for the first user, the next thing I am greeted with is Xscreensaver's login. So I actually need to log in twice, in two different ways, to get back to the original session. This happens even if I am only out of the original user's desktop for a few seconds. I would expect that the login screen should get me fully back to my original desktop without needing to enter the password a second time at the Xscreensaver. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xscreensaver 5.15-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 20:45:49 2013 InstallationDate: Installed on 2013-03-09 (42 days ago) InstallationMedia: Lubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130308) MarkForUpload: True SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1170987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 990727] Re: Can't assign keybinding Ctrl-Alt-w
I am also affected by this bug in 12.10. When I want to set Ctrl+shift+w for accessing the web, it automatically takes me back one tab in unity settings. -- 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/990727 Title: Can't assign keybinding Ctrl-Alt-w Status in GNOME Control Center: Fix Released Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: In 12.04, I am unable to assign the keyboard shortcut Ctrl-Alt-w to anything. For example, if I go to System Settings - Keyboard - Shortcuts and try to modify the keybinding for Launch Web Browser to Ctrl-Alt-w, the window just returns to the main System Settings screen and the new keybinding is not assigned. This was with a fresh install of 12.04. Tried it with a new user as well and the same problem exists. I was able to do so without any issues in 11.10. This may be related to the issue in https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/863549. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/990727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097105] Re: PDF's are offset when printed with lpr, but not acroread
The work around above works great! Looking at the diff, this could also be a bug in the libpoppler, PDF rendering lib, package as both versions of the cups-filter packages depend on different versions of the libpoppler package -- 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/1097105 Title: PDF's are offset when printed with lpr, but not acroread Status in “cups” package in Ubuntu: Confirmed Bug description: When printing pdf files from evince or lpr the result is a pdf file that is offset and usually cliped at the top and right edge. The following file was used www.opensource.apple.com/source/cups/cups-136/cups/test/testfile.pdf from evince select scalling as none select auto rotate and center the result is a printout that is shifted up and left so that hte lower and left edges can be seen the expected result is that all sides should be clipped given the testfile prints at the extreme boarders This only happens with 12.10. The printer works fine on 12.04 with the exact same drivers installed. These drivers are installed on both computers. The printer in question is a Brother DCP7065DN LPR driverdeb 2.1.0-1 35 KB 2011.Apr.01 cupswrapper driverdeb 2.0.4-2 13 KB 2011.Apr.01 downloaded from http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_prn.html#DCP-7065DN This test file can be printed as expected from acroread. The difference I believe is that evince and lpr pass along PDF and acroread passes postscript. this was observed by doing a file on the /var/spool/cups/d* This is also observed via libre office. when printing and one selects PDF for the 'printer language type' the offset is observed. if you select postscript from the 'printer language type' it prints as expected. I also have a MFC-J4510DW that prints perfectly from 12.10 all applications mentioned. Both printers have the latest firmware. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Jan 7 20:44:47 2013 InstallationDate: Installed on 2012-07-01 (190 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lpstat: device for DCP7065DN: lpd://DCP/BINARY_P1 device for MFCJ4510DW: lpd://MFC/BINARY_P1 MachineType: Hewlett-Packard HP G72 Notebook PC MarkForUpload: True Papersize: letter PpdFiles: DCP7065DN: Brother DCP7065DN for CUPS MFCJ4510DW: Brother MFC-J4510DW CUPS ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=9bc8d282-ff75-4e67-b337-cf110d979925 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-12-23 (15 days ago) dmi.bios.date: 02/15/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1439 dmi.board.vendor: Hewlett-Packard dmi.board.version: 60.4F dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd02/15/2011:svnHewlett-Packard:pnHPG72NotebookPC:pvr058E11252710001620100:rvnHewlett-Packard:rn1439:rvr60.4F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP G72 Notebook PC dmi.product.version: 058E11252710001620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1097105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1138251] Re: Desktop wallpaper Colors Gradients will not change color
Workaround added in #6 works great, thank you! -- 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/1138251 Title: Desktop wallpaper Colors Gradients will not change color Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce - System Settings - Appearances - Background Colors Gradients - Set a new sold color What happens - Background remains black. This is the same for solid colors and gradients What should happen - Background should change to new color ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 1 17:43:58 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] InstallationDate: Installed on 2013-02-11 (18 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210) MachineType: Dell Inc. Dell System XPS 15Z MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-8-generic root=UUID=93acc5a7-d531-4af3-a215-472a7bd065d6 ro acpi_backlight=vendor dell_laptop.backlight=0 quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 060G42 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.:bvrA04:bd07/27/2011:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS 15Z dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.03.01-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1138251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170987] Re: xscreensaver activates after logging in
This bug has affected me too for a long time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1170987 Title: xscreensaver activates after logging in Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Under certain conditions, Xscreensaver activates after a regular login thus requiring login credentials a second time in Lubuntu. When I switch users in LXDE and then log out of the second user I get the login screen, as expected. Then when I enter the login credentials for the first user, the next thing I am greeted with is Xscreensaver's login. So I actually need to log in twice, in two different ways, to get back to the original session. This happens even if I am only out of the original user's desktop for a few seconds. I would expect that the login screen should get me fully back to my original desktop without needing to enter the password a second time at the Xscreensaver. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xscreensaver 5.15-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 20:45:49 2013 InstallationDate: Installed on 2013-03-09 (42 days ago) InstallationMedia: Lubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130308) MarkForUpload: True SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1170987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170832] Re: Facebook Requires Authorization when already authorized
This affects me too, although I'm not using Pidgin. I am running 13.04 as well -- 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/1170832 Title: Facebook Requires Authorization when already authorized Status in “empathy” package in Ubuntu: Confirmed Bug description: I am running fully updated 13.04 64-bit. I simply cannot get empathy/UOA to connect to facebook. When I add the account in UOA everything seems to go well, facebook login page loads, it logs in successfully, facebook recognizes the session as safari on linux; but upon completing the setup in UOA empathy refuses to connect to it and keeps telling me it requires authorization. I've Tried the following: Removing the account from UOA Ending all active sessions on facebook and deleting the ubuntu app rebooting adding account in UOA, and allowing the ubuntu app to manage my messages etc... Didn't help at all. pidgin connects fine on the same computer. Sometimes it does let me add it and it works for a while, but eventually this issue happens again and leaves me totally unable to successfully add a facebook account for quite some time, until it randomly decides it wants to work again. Empathy/UOA in 13.04 has been unreliable to the point of ridiculousness, the application is basically unusable and can't handle the one basic task of an instant messaging program, which is connecting to my accounts reliably. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 19 16:57:50 2013 InstallationDate: Installed on 2013-04-17 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130416) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1170832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170832] Re: Facebook Requires Authorization when already authorized
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: empathy (Ubuntu) Status: New = Confirmed -- 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/1170832 Title: Facebook Requires Authorization when already authorized Status in “empathy” package in Ubuntu: Confirmed Bug description: I am running fully updated 13.04 64-bit. I simply cannot get empathy/UOA to connect to facebook. When I add the account in UOA everything seems to go well, facebook login page loads, it logs in successfully, facebook recognizes the session as safari on linux; but upon completing the setup in UOA empathy refuses to connect to it and keeps telling me it requires authorization. I've Tried the following: Removing the account from UOA Ending all active sessions on facebook and deleting the ubuntu app rebooting adding account in UOA, and allowing the ubuntu app to manage my messages etc... Didn't help at all. pidgin connects fine on the same computer. Sometimes it does let me add it and it works for a while, but eventually this issue happens again and leaves me totally unable to successfully add a facebook account for quite some time, until it randomly decides it wants to work again. Empathy/UOA in 13.04 has been unreliable to the point of ridiculousness, the application is basically unusable and can't handle the one basic task of an instant messaging program, which is connecting to my accounts reliably. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 19 16:57:50 2013 InstallationDate: Installed on 2013-04-17 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130416) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1170832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984785] Re: .goutputstream files polluting $HOME
For a while I thought this bug has been solved, but here I am looking at my $HOME forlder again. And what I see: -rw--- 1 root root 103 Apr 20 10:39 .Xauthority -rw-rw-r-- 1 user user 52 Apr 10 00:57 .Xauthority.2259UW Now what is that second one? Reminds me of good old '.goutputstream- 2259UW'. Even size is the same 52bytes, even `strings .Xauthority.2259UW` shows the same: localhost-pc MIT-MAGIC-COOKIE-1 One eye on strangeness, though i can't recall my actions on that timestamp -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME Status in The G Library - GLib: Fix Released Status in Light Display Manager: New Status in X.Org X server: New Status in “glib2.0” package in Ubuntu: Fix Committed Status in “lightdm” package in Ubuntu: Invalid Status in “glib2.0” source package in Precise: Triaged Status in “lightdm” source package in Precise: Invalid Bug description: .goutputstream files polluting $HOME. Which software or operation is creating these and why? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xauth 1:1.0.6-1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ati ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Wed Apr 18 13:29:31 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xauth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 474956] Re: odg export still doesn't work
** Changed in: inkscape Status: In Progress = Triaged ** Changed in: inkscape Assignee: Kris (kris-degussem) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/474956 Title: odg export still doesn't work Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Debian: Confirmed Bug description: I'm filing a fresh report since the search turned up stuff from 2007. I'm reporting the version of OOO Draw as 3.1.1, and Inkscape is 0.47. A binary tree drawing, exported to ODG, has several problems: - of the 7 circles in the picture, only one shows. This could be a problem with clones? Only the original shows and all the copies are missing. - the circle that is drawn has the wrong outline (stroke) width - the lines I drew are also the wrong stroke width - the lines are missing the arrow heads or other start/end markers and less critical, it didn't set the page size and drawing position. It seems that the SVG importer into Draw isn't working well either. It worked better on a slightly older version of Inkscape, so I wonder if there are changes in the way it writes things. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/474956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 474956] Re: odg export still doesn't work
Some more work done on the gradients in trunk r12286, which does not lead to correct showing a drawing with gradients (C++-code is improved, but still something is interfering with correct orientation). Reference to further improve the code: open document format specification https://www.oasis-open.org/committees/download.php/20847/OpenDocument-v1.1-cs1.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/474956 Title: odg export still doesn't work Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Debian: Confirmed Bug description: I'm filing a fresh report since the search turned up stuff from 2007. I'm reporting the version of OOO Draw as 3.1.1, and Inkscape is 0.47. A binary tree drawing, exported to ODG, has several problems: - of the 7 circles in the picture, only one shows. This could be a problem with clones? Only the original shows and all the copies are missing. - the circle that is drawn has the wrong outline (stroke) width - the lines I drew are also the wrong stroke width - the lines are missing the arrow heads or other start/end markers and less critical, it didn't set the page size and drawing position. It seems that the SVG importer into Draw isn't working well either. It worked better on a slightly older version of Inkscape, so I wonder if there are changes in the way it writes things. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/474956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170994] [NEW] Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2
Public bug reported: Hi, I did a fresh installed of ubuntu 12.04.2 on my netbook HP mini 1001tu After installing skype 4.1, I tested if the internal mic is working properly. And apparently it didn't work. The first attempt to solve this problem was referencing the following site: http://askubuntu.com/questions/155364/internal-microphone-not-working- on-hp-mini When I changed the setting: (terminal alsamixer F4: Capture Input Source) From Mic to Line I could then detect the internal mic working by PulseAudio Volume Control ( or using terminal pauvcontrol ) I could also make my internal mic working by using PulseAudio Volume Control (Tab [Input Devices] = Internal Sound Device, Analog Stereo = Port: ) From Analog Input to Line Input = The internal mic was working now, therefore I went on testing external mic/headphone jack (or hole? sorry for my bad English) It works with headphone, microphone, and also headset (the mix of headphone and mix both). But after I unplugged these devices, I found that the internal mic was not working anymore. It had to be re-configure again according to the procedures of solving internal mic fail. = The second attempt to achieve correct auto-switching behavior is trying to add settings to /etc/asound.conf or ~/.asoundrc (according to: http://wiki.audacityteam.org/wiki/USB_mic_on_Linux#Setting_default_recording_device) pcm.internal_mic { type hw slave.pcm=hw:0,0,1 } pcm.!default { type asym playback.pcm { type plug slave.pcm hw:0,0 } capture.pcm { type plug slave.pcm internal_mic } } I have tested hw:0,0,1 is the presence of internal mic with arecord -f dat -d 2 -D hw:0,0,1 test.wav Unfortunately, this didn't work as expected. The auto-switching is still not working properly. I think this is reproducible, so I post this as a bug report. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa pulseaudio sound ** Description changed: Hi, I did a fresh installed of ubuntu 12.04.2 on my netbook HP mini 1001tu After installing skype 4.1, I tested if the internal mic is working properly. And apparently it didn't work. The first attempt to solve this problem was referencing the following site: http://askubuntu.com/questions/155364/internal-microphone-not-working- on-hp-mini When I changed the setting: - (terminal alsamixer F4: Capture Input Source) + (terminal alsamixer F4: Capture Input Source) From Mic to Line I could then detect the internal mic working by PulseAudio Volume Control ( or using terminal pauvcontrol ) I could also make my internal mic working by using PulseAudio Volume Control (Tab [Input Devices] = Internal Sound Device, Analog Stereo = Port: ) From Analog Input to Line Input = The internal mic was working now, therefore I went on testing external mic/headphone jack (or hole? sorry for my bad English) It works with headphone, microphone, and also headset (the mix of headphone and mix both). But after I unplugged these devices, I found that the internal mic was not working anymore. It had to be re-configure again according to the procedures of solving internal mic fail. = The second attempt to achieve correct auto-switching behavior is trying to add settings to /etc/asound.conf or ~/.asoundrc (according to: http://wiki.audacityteam.org/wiki/USB_mic_on_Linux#Setting_default_recording_device) pcm.internal_mic { - type hw - slave.pcm=hw:0,0,1 + type hw + slave.pcm=hw:0,0,1 } - pcm.!default + pcm.!default { - type asym - playback.pcm { - type plug - slave.pcm hw:0,0 - } - capture.pcm { - type plug - slave.pcm internal_mic - } - } + type asym + playback.pcm { + type plug + slave.pcm hw:0,0 + } + capture.pcm { + type plug + slave.pcm internal_mic + } + } I have tested hw:0,0,1 is the presence of internal mic with arecord -f dat -d 2 -D hw:0,0,1 test.wav Unfortunately, this didn't work as expected. The auto-switching is still not working properly. I think this is reproducible, so I post this as a bug report. ** Tags added: alsa sound -- 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/1170994 Title: Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2 Status in “alsa-driver” package in Ubuntu: New Bug description: Hi, I did a fresh installed of ubuntu 12.04.2 on my netbook HP mini 1001tu After
[Desktop-packages] [Bug 863663] Re: Gnome-shell and ambiance theme icon issue
Thanks #5! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-mono in Ubuntu. https://bugs.launchpad.net/bugs/863663 Title: Gnome-shell and ambiance theme icon issue Status in Light Themes: Invalid Status in “humanity-icon-theme” package in Ubuntu: Confirmed Status in “ubuntu-mono” package in Ubuntu: Confirmed Bug description: the ambiance theme works nicely in Gnome-Shell now after beta 2, and the unity icon theme 'Ubuntu-mono-dark' almost fits perfectly. The only issues I have found with the perfect implementation of the ubuntu icon theme in gnome-shell is the Battery icon is very very small, and the volume increase/decrease pop up is very pixelated. Is it possible to fix the icon theme or Gnome-shell to make these look nice? I am using Adawaita right now, just because those icons bug me. If they were to get fixed I could just use Ambiance for both my Gnome- Shell and Unity To manage notifications about this bug go to: https://bugs.launchpad.net/light-themes/+bug/863663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170994] Re: Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2
** Attachment added: ALSA info by alsa-info.sh https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1170994/+attachment/3649302/+files/alsa-info.txt -- 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/1170994 Title: Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2 Status in “alsa-driver” package in Ubuntu: New Bug description: Hi, I did a fresh installed of ubuntu 12.04.2 on my netbook HP mini 1001tu After installing skype 4.1, I tested if the internal mic is working properly. And apparently it didn't work. The first attempt to solve this problem was referencing the following site: http://askubuntu.com/questions/155364/internal-microphone-not-working- on-hp-mini When I changed the setting: (terminal alsamixer F4: Capture Input Source) From Mic to Line I could then detect the internal mic working by PulseAudio Volume Control ( or using terminal pauvcontrol ) I could also make my internal mic working by using PulseAudio Volume Control (Tab [Input Devices] = Internal Sound Device, Analog Stereo = Port: ) From Analog Input to Line Input = The internal mic was working now, therefore I went on testing external mic/headphone jack (or hole? sorry for my bad English) It works with headphone, microphone, and also headset (the mix of headphone and mix both). But after I unplugged these devices, I found that the internal mic was not working anymore. It had to be re-configure again according to the procedures of solving internal mic fail. = The second attempt to achieve correct auto-switching behavior is trying to add settings to /etc/asound.conf or ~/.asoundrc (according to: http://wiki.audacityteam.org/wiki/USB_mic_on_Linux#Setting_default_recording_device) pcm.internal_mic { type hw slave.pcm=hw:0,0,1 } pcm.!default { type asym playback.pcm { type plug slave.pcm hw:0,0 } capture.pcm { type plug slave.pcm internal_mic } } I have tested hw:0,0,1 is the presence of internal mic with arecord -f dat -d 2 -D hw:0,0,1 test.wav Unfortunately, this didn't work as expected. The auto-switching is still not working properly. I think this is reproducible, so I post this as a bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1170994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993914] Re: subwoofer problems on Dell XPS 15
I am also facing problem in dell xps l502x on ubuntu 12.10. subwoofer volume is very high so getting ticking sound from woofer. is there any way to lower the woofer volume. -- 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/993914 Title: subwoofer problems on Dell XPS 15 Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: When I play music on my Dell XPS 15 (L502X) with ubuntu 12. 04, it seems as if the subwoofer is not working - the subwoofer volume control is disabled in system settings. The sound quality is pretty poor in comparison to the quality when I had Windows 7. The sound via the audio jack is just fine. Alsa info: http://www.alsa-project.org/db/?f=cbdbb9f190a11e232bb13f571f0300efe2cfb262 I'm using the stable version of all packages. All help is appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/993914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170994] Re: Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2
This source did the same as I did, but also mentioned that they have to manually configure this every reboot https://getsatisfaction.com/jolicloud/topics/internal_mic_doesnt_work_on_hp_mini_1000 ( I just notice that plug unplug can reproduce this, too. ) -- 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/1170994 Title: Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2 Status in “alsa-driver” package in Ubuntu: New Bug description: Hi, I did a fresh installed of ubuntu 12.04.2 on my netbook HP mini 1001tu After installing skype 4.1, I tested if the internal mic is working properly. And apparently it didn't work. The first attempt to solve this problem was referencing the following site: http://askubuntu.com/questions/155364/internal-microphone-not-working- on-hp-mini When I changed the setting: (terminal alsamixer F4: Capture Input Source) From Mic to Line I could then detect the internal mic working by PulseAudio Volume Control ( or using terminal pauvcontrol ) I could also make my internal mic working by using PulseAudio Volume Control (Tab [Input Devices] = Internal Sound Device, Analog Stereo = Port: ) From Analog Input to Line Input = The internal mic was working now, therefore I went on testing external mic/headphone jack (or hole? sorry for my bad English) It works with headphone, microphone, and also headset (the mix of headphone and mix both). But after I unplugged these devices, I found that the internal mic was not working anymore. It had to be re-configure again according to the procedures of solving internal mic fail. = The second attempt to achieve correct auto-switching behavior is trying to add settings to /etc/asound.conf or ~/.asoundrc (according to: http://wiki.audacityteam.org/wiki/USB_mic_on_Linux#Setting_default_recording_device) pcm.internal_mic { type hw slave.pcm=hw:0,0,1 } pcm.!default { type asym playback.pcm { type plug slave.pcm hw:0,0 } capture.pcm { type plug slave.pcm internal_mic } } I have tested hw:0,0,1 is the presence of internal mic with arecord -f dat -d 2 -D hw:0,0,1 test.wav Unfortunately, this didn't work as expected. The auto-switching is still not working properly. I think this is reproducible, so I post this as a bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1170994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170952] Re: icons not added to launcher
** Description changed: Hallo Not sure if this is a software-center or unity bug. - When I installa new application via software-center, it is no more automatically added to the launcher, is this a new behavior ? + When I install a new application via software-center, it is no more automatically added to the launcher, is this a new behavior ? Thanks Fabio - ProblemType: Bug - DistroRelease: Ubuntu 13.04 + ProblemType: BugDistroRelease: Ubuntu 13.04 Package: software-center 5.6.0-0ubuntu2 Uname: Linux 3.9.0-030900rc3-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 16:14:04 2013 InstallationDate: Installed on 2013-02-22 (56 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130222) MarkForUpload: True PackageArchitecture: all ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=it_IT.UTF-8 - SHELL=/bin/bash - SourcePackage: software-center + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=it_IT.UTF-8 + SHELL=/bin/bashSourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1170952 Title: icons not added to launcher Status in “software-center” package in Ubuntu: New Bug description: Hallo Not sure if this is a software-center or unity bug. When I install a new application via software-center, it is no more automatically added to the launcher, is this a new behavior ? Thanks Fabio ProblemType: BugDistroRelease: Ubuntu 13.04 Package: software-center 5.6.0-0ubuntu2 Uname: Linux 3.9.0-030900rc3-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 20 16:14:04 2013 InstallationDate: Installed on 2013-02-22 (56 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130222) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bashSourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1170952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 875195] Re: Screen is very dim after turning on Laptop
I have an ASUS UL30A laptop with Intel® GMA X4500MHD graphics card and I have had this problem ever since I started using Ubuntu (10.04). Now I run 12.04 and the problem persists. I have tried everything but nothing works except going to Brightness and Lock, decreasing Brightness to the minimum and then increasing it again. I have to do this everytime I log in or after unlocking the screen. By the way I don't have Dim screen to save power checked, Turn screen off when inactive for is set to Never and Lock is OFF but never the less the screen dims and locks. So neither of the options on the Brightness and Lock works for me. -- 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/875195 Title: Screen is very dim after turning on Laptop Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: Installed Ubuntu 11.10 64bit on my Fujitsu Esprimo Mobile V6555 laptop. Every time when turned on, the screen is extremely dim. Brightness up combination (Fn+F9) doesn't work. Need to go to System settings - Screen and rise brightness from there. I rise it there to the max and the brightness is still not maximal. Then I need to press Fn+F9 once to rise it to the brightest. I need to do it every time my laptop turns on. This did NOT happen in Ubuntu 10.10 and 11.04 that were installed on this same laptop earlier. ProblemType: Bug DistroRelease: Ubuntu 11.10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Sat Oct 15 19:55:49 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (nautilus:1615): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed (nautilus:1615): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/875195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 890041] Re: Untitle Document opens when opening a document using `gksu[do] gedit /path/to/file`.
*** This bug is a duplicate of bug 796076 *** https://bugs.launchpad.net/bugs/796076 When opening gedit from dolphin you can fix this annoying problem by modifying the line that lauches the program. Change: gedit %U into: gedit %U /dev/null A similar fix for launching from the command line is discussed here: http://ubuntuforums.org/showthread.php?t=2029114 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/890041 Title: Untitle Document opens when opening a document using `gksu[do] gedit /path/to/file`. Status in “gedit” package in Ubuntu: Confirmed Bug description: $ gedit # opens untitled document $ gedit /path/to/file # opens file $ sudo gedit /path/to/file # opens file $ gksu gedit /path/to/file # opens file untitled document $ gksudo gedit /path/to/file # opens file untitled document The Untitled Document should only be opened when no file is provided, according to `man gedit`. Additionally, when Untitled Document is opened unexpectedly via gksu[do], its tab icon is shown as the rotating loading icon. Occasionally the icon will stop spinning, when the tab is focused /un-focused it will continue spinning, until it freezes again. On the other had, when I expect Untitled Document to be opened (e.g. `gedit`), its tab icon is the proper plain-text icon. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gedit 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CheckboxSubmission: 880f1cef728a67d1a58407cc143447d4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Sun Nov 13 21:07:37 2011 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) SourcePackage: gedit UpgradeStatus: Upgraded to oneiric on 2011-11-04 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/890041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1016252] Re: transmission-daemon checks ~/.config/user-dirs.dirs of a non-root user
I installed transmission-daemon version 1.93 (10621) on a headless server running 10.04lts, following the instructions here: http://1000umbrellas.com/2010/10/04/updated-transmission- installationconfiguration-on-ubuntu-server and I am seeing the exact same issue. I am having anotherdifferent issue as well but I will report that separately. ** Changed in: transmission (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1016252 Title: transmission-daemon checks ~/.config/user-dirs.dirs of a non-root user Status in “transmission” package in Ubuntu: New Bug description: 1. sudo apt-get install transmission-daemon transmission-daemon installs. This is printed when it starts (which it does immediately): [22:00:02.367] Couldn't read /home/user/.config/user-dirs.dirs: Permission denied Why is it doing this? Even if I sudo -s before the install it's still checking the local user's config files. Why? Why has it picked this user? It shouldn't be doing this. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: transmission-daemon 1.93-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-41.90-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-41-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Jun 21 22:00:29 2012 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: transmission To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1016252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1097903] Re: lightdm-session fails if user's .profile has non-posix sh init.
*** This bug is a duplicate of bug 678421 *** https://bugs.launchpad.net/bugs/678421 ** This bug has been marked a duplicate of bug 678421 Error message for a faulty ~/.profile script -- 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/1097903 Title: lightdm-session fails if user's .profile has non-posix sh init. Status in “lightdm” package in Ubuntu: Confirmed Bug description: I don't actually mind the failure (its a feature!) The problem is that if the user's .profile has non-posix sh in it (causing /usr/sbin /lightdm-session to basically crash) there is no good presentation to the user about this. The user tries to login. Lightdm tries to source their ~/.profile, and crashes if they have non-posix sh in them. lightdm simply restarts and drops the user back at the login screen. There is no reporting to the user what happened, so they can fix the problem. What is worse, is that the failsafe session doesn't work either. -A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1097903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170609] Re: No french translation for choqok 1.3 in kubuntu 13.04 although it is translated in french
Hi, thank you for taking your time to report this bug and helping to make kubuntu better. The 1.3 version that was taken from debian doesn't quite match up with the official 1.3 release. It's being looked at. ** Tags added: kubuntu raring ** Changed in: choqok (Ubuntu) Importance: Undecided = Medium ** Changed in: choqok (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to choqok in Ubuntu. https://bugs.launchpad.net/bugs/1170609 Title: No french translation for choqok 1.3 in kubuntu 13.04 although it is translated in french Status in “choqok” package in Ubuntu: Triaged Bug description: OS: Kubuntu 13.04 32b package: choqok 1.3 KDE: 4.10.2 There is no french translation for choqok 1.3 in Kubuntu 13.04 although this app is fully translated in french. Moreover a french .po file is provided in the source tarball of choqok 1.3. So if we can make adjustment it will be good! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/choqok/+bug/1170609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
I've put up packages with that commit backported here if anyone wants to try it https://launchpad.net/~sarvatt/+archive/sru1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37) plugins: probing /usr/lib/purple-2/simfix.so (16:52:37) plugins: probing /usr/lib/purple-2/libstatusnet.so (16:52:37) twitterim: plugin_init (16:52:37) twitterim: plugin = 0x7f658884bd30 (16:52:37) plugins: probing /usr/lib/purple-2/oldlogger.so (16:52:37) plugins: probing /usr/lib/purple-2/autoprofile.so (16:52:37) autoprofile: general: Initializing AutoProfile (16:52:37) autoprofile: general: Initializing preference
[Desktop-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
Marked bug #1097903 a duplicate of this one, and added a lightdm (ubuntu) task. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Importance: Undecided = Low ** Changed in: lightdm (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/678421 Title: Error message for a faulty ~/.profile script Status in “gdm” package in Ubuntu: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: Binary package hint: gdm After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile made the Xorg startup fail. (At that moment I had already forgotten the changes made to the .profile). As I had autologin that meant it kept trying to login and finally showed me the graphics reconfiguration screen. That sent me to a huge hunt for xorg conf and setup problems. Anyway finally tracked this down. I had used bash syntax in .profile file whereas it was run with sh. This is not a bug per se but I think a user mistake in .profile shouldn't bring the whole xorg startup to a halt as it does with autologin. I propose running user .profile and .xprofile scripts so that Xsession script continues running even if they have errors. I'm not sure whether this change would have some negative effects as well. 1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010 i686 GNU/Linux 2) gdm 2.30.2.is.2.30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 990951] Re: Empathy Messenger 3.4.1: avatars not showing [Windows Live protocol] [Ubuntu 12.04]
the problem is not solved yet! -- 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/990951 Title: Empathy Messenger 3.4.1: avatars not showing [Windows Live protocol] [Ubuntu 12.04] Status in Chat app, and Telepathy user interface: Unknown Status in “empathy” package in Ubuntu: Invalid Bug description: Hello I just did a clean install of Ubuntu 12.04 and It has pre- installed Empathy 3.4.1 but I have an issue : I can't see my contact's avatars while i am using windows live protocol. On Ubuntu 11.04 I was able to see my contact's pictures. I think Empathy's version was 3.2 (I am not sure) What can I do to fix this issue ? Empathy 3.4.1 is stable or beta version ? ps : I attach a debug file and apport infos ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sun Apr 29 10:49:55 2012 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1720): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed (gnome-settings-daemon:1704): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `window-update_and_descendants_freeze_count 0' failed (empathy:2446): folks-WARNING **: Failed to reach quiescence normally (0 backends and 1 persona stores still haven't reached quiescence). Forcing IndividualAggregator quiescence due to reaching the timeout. (ubuntu-tweak:2680): GConf-WARNING **: : You can't use a GConfEngine that has an active GConfClient wrapper object. Use GConfClient API instead. (ubuntu-tweak:2680): GConf-WARNING **: : You can't use a GConfEngine that has an active GConfClient wrapper object. Use GConfClient API instead. To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/990951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1170609] Re: No french translation for choqok 1.3 in kubuntu 13.04 although it is translated in french
** Changed in: choqok (Ubuntu) Assignee: (unassigned) = Philip Muškovac (yofel) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to choqok in Ubuntu. https://bugs.launchpad.net/bugs/1170609 Title: No french translation for choqok 1.3 in kubuntu 13.04 although it is translated in french Status in “choqok” package in Ubuntu: Triaged Bug description: OS: Kubuntu 13.04 32b package: choqok 1.3 KDE: 4.10.2 There is no french translation for choqok 1.3 in Kubuntu 13.04 although this app is fully translated in french. Moreover a french .po file is provided in the source tarball of choqok 1.3. So if we can make adjustment it will be good! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/choqok/+bug/1170609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1167573] Re: pidgin freezes / crashes
*** This bug is a duplicate of bug 1108056 *** https://bugs.launchpad.net/bugs/1108056 ** This bug has been marked a duplicate of bug 1108056 fetching URLs freezes pidgin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1167573 Title: pidgin freezes / crashes Status in “pidgin” package in Ubuntu: New Bug description: it just seem to hang... i have to kill -KILL it... a gdb backtrace reveals this here: Program received signal SIGPIPE, Broken pipe. 0x74b36c5d in write () from /lib/x86_64-linux-gnu/libpthread.so.0 (gdb) bt #0 0x74b36c5d in write () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fffe5807927 in irc_send_len () from /usr/lib/purple-2/libirc.so #2 0x7fffe5805359 in irc_cmd_quit () from /usr/lib/purple-2/libirc.so #3 0x7fffe58068c7 in ?? () from /usr/lib/purple-2/libirc.so #4 0x750a3f26 in _purple_connection_destroy () from /usr/lib/libpurple.so.0 #5 0x7508fa5e in purple_account_disconnect () from /usr/lib/libpurple.so.0 #6 0x750a31c5 in ?? () from /usr/lib/libpurple.so.0 #7 0x753c6b1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x753c5f05 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x753c6248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x753c66ba in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7663efe7 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #12 0x5558f419 in main () ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Wed Apr 10 22:55:24 2013 InstallationDate: Installed on 2011-03-29 (743 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin UpgradeStatus: Upgraded to raring on 2013-04-05 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1167573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
debdiff containing the fix targeting raring-proposed for SRU since we are past final freeze and its seeded in lubuntu. pidgin (1:2.10.7-0ubuntu4.1) raring-proposed; urgency=low * Add hg-remove-SIGCHLD-handler.patch: Fix hanging on startup. Backport of upstream commit from 3.0 (LP: #1108056) -- Robert Hooker sarv...@ubuntu.com Sat, 20 Apr 2013 15:40:16 -0400 ** Patch added: pidgin_2.10.7-0ubuntu4.1.debdiff https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1108056/+attachment/3649393/+files/pidgin_2.10.7-0ubuntu4.1.debdiff ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37)
[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
It is working like a champ here, I've done ~100 startups and toggled wifi on and off a bunch of times (that also would make it hang) and have had no hangs at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37) plugins: probing /usr/lib/purple-2/simfix.so (16:52:37) plugins: probing /usr/lib/purple-2/libstatusnet.so (16:52:37) twitterim: plugin_init (16:52:37) twitterim: plugin = 0x7f658884bd30 (16:52:37) plugins: probing /usr/lib/purple-2/oldlogger.so (16:52:37) plugins: probing /usr/lib/purple-2/autoprofile.so (16:52:37) autoprofile: general: Initializing AutoProfile (16:52:37) autoprofile:
[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
$ sudo gdebi pidgin_2.10.7-0ubuntu5~lp1108056_amd64.deb libpurple0_2.10.7-0ubuntu5~lp1108056_amd64.deb pidgin-dbg_2.10.7-0ubuntu5~lp1108056_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Building data structures... Done Building data structures... Done This package is uninstallable Breaks existing package 'pidgin-dbg' dependency pidgin (= 1:2.10.7-0ubuntu4) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37) plugins: probing /usr/lib/purple-2/simfix.so (16:52:37) plugins: probing /usr/lib/purple-2/libstatusnet.so (16:52:37) twitterim: plugin_init
[Desktop-packages] [Bug 1153935] Re: pidgin freezes on startup
*** This bug is a duplicate of bug 1108056 *** https://bugs.launchpad.net/bugs/1108056 ** This bug is no longer a duplicate of bug 1109251 pidgin hangs on startup ** This bug has been marked a duplicate of bug 1108056 fetching URLs freezes pidgin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1153935 Title: pidgin freezes on startup Status in “pidgin” package in Ubuntu: Confirmed Bug description: Pidgin's buddy list-window quite often just freezes on startup. Needs to be killed in order to get anything to work. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.7-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2 Uname: Linux 3.8.0-12-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Mon Mar 11 23:06:41 2013 InstallationDate: Installed on 2013-01-21 (48 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130121) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1153935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1109251] Re: pidgin hangs on startup
*** This bug is a duplicate of bug 1108056 *** https://bugs.launchpad.net/bugs/1108056 ** This bug has been marked a duplicate of bug 1108056 fetching URLs freezes pidgin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1109251 Title: pidgin hangs on startup Status in “pidgin” package in Ubuntu: Confirmed Bug description: After upgrading to a recent set of bits in raring, pidgin reliably hangs on startup. This is a regression from 12.10. To reproduce: 1) Launch pidgin Expected results: The Buddy List window loads a list of buddies (IRC channels in my case), and pidgin opens a new chat window to auto-join a set of IRC channels Actual results: The Buddy List window is created but it's completely blank - there is no content at all, not even the account status popup menu. The OS greys out the Buddy List window. Pidgin is completely unresponsive. GDB shows pidgin is hung in purple_gnome_proxy_get_parameter: Thread 1 (Thread 0x7f3629f809c0 (LWP 2713)): #0 0x7f362681339d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f362738b87c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f362738bd52 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f36273cd3e1 in g_spawn_sync () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f36273cd858 in g_spawn_command_line_sync () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f36270942ad in purple_gnome_proxy_get_parameter (gnome_version=optimized out, parameter=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:270 #6 purple_gnome_proxy_get_parameter (parameter=optimized out, gnome_version=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:260 #7 0x7f3627094920 in purple_gnome_proxy_get_info () at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:307 #8 purple_proxy_get_setup (account=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:2257 #9 0x7f36270a5102 in initiate_resolving (data=0x7f362bdf6040) at /build/buildd/pidgin-2.10.6/./libpurple/dnsquery.c:896 #10 0x7f362738c1ab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f362738b5a5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f362738b8e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f362738bd52 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f3628601f17 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #15 0x7f3629ffd119 in main (argc=1, argv=0x7fffaf9259d8) at /build/buildd/pidgin-2.10.6/./pidgin/gtkmain.c:933 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.6-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 29 15:13:17 2013 InstallationDate: Installed on 2010-09-17 (865 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin UpgradeStatus: Upgraded to raring on 2013-01-25 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1109251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
OK, not all packages were available when I tried! now seems it upgraded fine. so far it's working! thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37) plugins: probing /usr/lib/purple-2/simfix.so (16:52:37) plugins: probing /usr/lib/purple-2/libstatusnet.so (16:52:37) twitterim: plugin_init (16:52:37) twitterim: plugin = 0x7f658884bd30 (16:52:37) plugins: probing /usr/lib/purple-2/oldlogger.so (16:52:37) plugins: probing /usr/lib/purple-2/autoprofile.so (16:52:37) autoprofile: general: Initializing AutoProfile (16:52:37) autoprofile: general: Initializing preference defaults if necessary
[Desktop-packages] [Bug 1103555] Re: pidgin hung after start
*** This bug is a duplicate of bug 1108056 *** https://bugs.launchpad.net/bugs/1108056 ** This bug is no longer a duplicate of bug 1098207 pidgin hangs ** This bug has been marked a duplicate of bug 1108056 fetching URLs freezes pidgin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1103555 Title: pidgin hung after start Status in “pidgin” package in Ubuntu: Confirmed Bug description: started pidgin, hung immediately after showing up the gui. auto-logon seems to be in progress but the ui is not responsive and the process must be killed ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.6-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Wed Jan 23 18:02:49 2013 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2012-10-07 (108 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120926) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1103555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102995] Re: pidgin freezes without error message
*** This bug is a duplicate of bug 1108056 *** https://bugs.launchpad.net/bugs/1108056 ** This bug is no longer a duplicate of bug 1098207 pidgin hangs ** This bug has been marked a duplicate of bug 1108056 fetching URLs freezes pidgin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1102995 Title: pidgin freezes without error message Status in “pidgin” package in Ubuntu: Confirmed Bug description: Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 pidgin: Instalado: 1:2.10.6-0ubuntu3 Candidato: 1:2.10.6-0ubuntu3 Tabela de versão: *** 1:2.10.6-0ubuntu3 0 500 http://br.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status Pidgin freeze a lot of time without error message. I need to force close. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.6-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 22 11:30:27 2013 InstallationDate: Installed on 2012-12-22 (30 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: Upgraded to raring on 2013-01-09 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1102995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1098207] Re: pidgin hangs
*** This bug is a duplicate of bug 1108056 *** https://bugs.launchpad.net/bugs/1108056 ** This bug has been marked a duplicate of bug 1108056 fetching URLs freezes pidgin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1098207 Title: pidgin hangs Status in “pidgin” package in Ubuntu: Confirmed Bug description: Pidgin hangs from time to time. It seems to be some problem related to thread locking, gst or pulseaudio. Backtrace attached. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.6-0ubuntu3 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 10 15:32:09 2013 MarkForUpload: True SourcePackage: pidgin UpgradeStatus: Upgraded to raring on 2012-12-03 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1098207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
you forgot pidgin-data and libpurple-bin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37) plugins: probing /usr/lib/purple-2/simfix.so (16:52:37) plugins: probing /usr/lib/purple-2/libstatusnet.so (16:52:37) twitterim: plugin_init (16:52:37) twitterim: plugin = 0x7f658884bd30 (16:52:37) plugins: probing /usr/lib/purple-2/oldlogger.so (16:52:37) plugins: probing /usr/lib/purple-2/autoprofile.so (16:52:37) autoprofile: general: Initializing AutoProfile (16:52:37) autoprofile: general: Initializing preference defaults if necessary (16:52:37) plugins: probing /usr/lib/purple-2/pidgin-libnotify.so
[Desktop-packages] [Bug 1170994] Re: Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2
I finally able to control the behavior according to: http://voices.canonical.com/david.henningsson/2011/11/29/turn-your-mic- jack-into-a-headphone-jack/ David Henningsoom's hda-jack-retask package === But actually it still reveals a problem: The alsa-driver seems correctly detects internal mic at Pin ID: 0x0e but pulseaudio map it to Line-in input, which is not a proper mapping I use hda-jack-retask to override it as Internal mic Then everything works now, including replugging of headset/headphone/ext mic ** Package changed: alsa-driver (Ubuntu) = pulseaudio (Ubuntu) -- 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/1170994 Title: Internal Mic is not working properly on HP mini 1001tu, ubuntu 12.04.2 Status in “pulseaudio” package in Ubuntu: New Bug description: Hi, I did a fresh installed of ubuntu 12.04.2 on my netbook HP mini 1001tu After installing skype 4.1, I tested if the internal mic is working properly. And apparently it didn't work. The first attempt to solve this problem was referencing the following site: http://askubuntu.com/questions/155364/internal-microphone-not-working- on-hp-mini When I changed the setting: (terminal alsamixer F4: Capture Input Source) From Mic to Line I could then detect the internal mic working by PulseAudio Volume Control ( or using terminal pauvcontrol ) I could also make my internal mic working by using PulseAudio Volume Control (Tab [Input Devices] = Internal Sound Device, Analog Stereo = Port: ) From Analog Input to Line Input = The internal mic was working now, therefore I went on testing external mic/headphone jack (or hole? sorry for my bad English) It works with headphone, microphone, and also headset (the mix of headphone and mix both). But after I unplugged these devices, I found that the internal mic was not working anymore. It had to be re-configure again according to the procedures of solving internal mic fail. = The second attempt to achieve correct auto-switching behavior is trying to add settings to /etc/asound.conf or ~/.asoundrc (according to: http://wiki.audacityteam.org/wiki/USB_mic_on_Linux#Setting_default_recording_device) pcm.internal_mic { type hw slave.pcm=hw:0,0,1 } pcm.!default { type asym playback.pcm { type plug slave.pcm hw:0,0 } capture.pcm { type plug slave.pcm internal_mic } } I have tested hw:0,0,1 is the presence of internal mic with arecord -f dat -d 2 -D hw:0,0,1 test.wav Unfortunately, this didn't work as expected. The auto-switching is still not working properly. I think this is reproducible, so I post this as a bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1170994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp