[Desktop-packages] [Bug 1362368] Re: Enable compilation of Unity messaging menu integration
I can only see the version 1:2.10.9-0ubuntu3.1 in repos. http://packages.ubuntu.com/search?keywords=pidgin Has this fix been actually released? -- 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/1362368 Title: Enable compilation of Unity messaging menu integration Status in “pidgin” package in Ubuntu: Fix Released Bug description: Pidgin has messaging menu integration since several releases, but it seems it is not compiled by default. Please compile with --enable-unity libunity-dev and libmessaging-menu-dev are build dependencies then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1362368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1362368] Re: Enable compilation of Unity messaging menu integration
Sorry, I see what happened. It's only released for Utopic. Can this be backported to Trusty? Since it's a LTS, I think this fix should hit the repos. -- 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/1362368 Title: Enable compilation of Unity messaging menu integration Status in “pidgin” package in Ubuntu: Fix Released Bug description: Pidgin has messaging menu integration since several releases, but it seems it is not compiled by default. Please compile with --enable-unity libunity-dev and libmessaging-menu-dev are build dependencies then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1362368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278569] Re: ibus breaks emacs and eclipse control-space keybinding
I'm unable to setup a different keybinding system-wide. There is a file describing the dconf schema with the default values: /usr/share/glib-2.0/schemas/org.freedesktop.ibus.gschema.xml I tried changing this: [ 'space' ]Trigger shortcut keys for gtk_accelerator_parseThe shortcut keys for turning input method on or off To this: [ ' space' ]Trigger shortcut keys for gtk_accelerator_parseThe shortcut keys for turning input method on or off I can see the change in dconf-editor. If I set the value to the default, I get ['space'] and the bold style on the key is removed. But when I enter ibus-setup, the old default space is shown instead. Changing the value to space inside ibus-setup, also makes changes that I can see in dconf-editor. The value is not set to the default (bold style in key), and the very same ['space'] string is shown. If I press the "Reset to defaults" button in dconf-editor, the value is set to the default (the bold style on the key is gone). The string is still the same ['space'] Then, If I enter ibus-setup again, space is shown. I should be able to setup a different system-wide keybinding by changing this file, shouldn't I? Should I file a bug report? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1278569 Title: ibus breaks emacs and eclipse control-space keybinding Status in “ibus” package in Ubuntu: Triaged Bug description: Installing ibus 1.5.5-1ubuntu1 breaks Emacs 24's control-space keybinding. I generally have that bound to a custom lisp function, but by default (e.g. starting with `emacs -Q`) it is bound to set- mark-command. After doing a dist-upgrade in Trusty which installs ibus 1.5.5-1ubuntu1, emacs no longer even sees the control-space key chord. My guess is that ibus is consuming this event, preventing emacs from seeing it. This is a critical regression that makes emacs almost unusable. By process of elimination, I've narrowed it down to one of these 4 binary packages. gir1.2-ibus-1.0 ibus ibus-gtk ibus-gtk3 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 10 15:15:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-06 (66 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1278569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1312135] Re: Under KDE firefox uses nautilus instead of dolphin to handle directories
I can't remove it. long story short, I'm in a large network with multiple computers running Ubuntu, all with the same setup. I can't just uninstall Nautilus from one of them. Fortunately, I tried again the workaround and it worked. I probably made something wrong the first time, sorry. The changes are being rolled out to all the computers over the network. I hope I won't break anything with it. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1312135 Title: Under KDE firefox uses nautilus instead of dolphin to handle directories Status in “firefox” package in Ubuntu: Confirmed Bug description: 1. Run firefox under kde 2. Download a file with it 3. Click the download icon 4. Right click on the download object 5. Ask to open the containing folder I would expect the KDE file browser "dolphin" to open. What instead happens the GNOME file browser "nautilus" is opened without the needed icons. (see screenshot). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 28.0+build2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: enzo 2178 F pulseaudio enzo 2301 F pulseaudio /dev/snd/controlC0: enzo 2178 F pulseaudio enzo 2301 F pulseaudio BuildID: 20140410211200 Channel: Unavailable CurrentDesktop: KDE Date: Thu Apr 24 13:43:20 2014 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2014-04-23 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IpRoute: default via 192.168.254.254 dev eth0 proto static 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.254.0/24 dev eth0 proto kernel scope link src 192.168.254.42 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200 RfKill: RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L02 v02.01 dmi.board.asset.tag: CZC3523T17 dmi.board.name: 18EB dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3523T17 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP ProDesk 490 G1 MT dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1312135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1312135] Re: Under KDE firefox uses nautilus instead of dolphin to handle directories
I have tried the workaround from #5, but nautilus is still being opened! :( Launching nautilus from the command line opens dolphin instead, but Firefox always launches nautilus. Weird, huh? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1312135 Title: Under KDE firefox uses nautilus instead of dolphin to handle directories Status in “firefox” package in Ubuntu: Confirmed Bug description: 1. Run firefox under kde 2. Download a file with it 3. Click the download icon 4. Right click on the download object 5. Ask to open the containing folder I would expect the KDE file browser "dolphin" to open. What instead happens the GNOME file browser "nautilus" is opened without the needed icons. (see screenshot). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 28.0+build2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: enzo 2178 F pulseaudio enzo 2301 F pulseaudio /dev/snd/controlC0: enzo 2178 F pulseaudio enzo 2301 F pulseaudio BuildID: 20140410211200 Channel: Unavailable CurrentDesktop: KDE Date: Thu Apr 24 13:43:20 2014 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2014-04-23 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) IpRoute: default via 192.168.254.254 dev eth0 proto static 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.254.0/24 dev eth0 proto kernel scope link src 192.168.254.42 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200 RfKill: RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L02 v02.01 dmi.board.asset.tag: CZC3523T17 dmi.board.name: 18EB dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3523T17 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP ProDesk 490 G1 MT dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1312135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
Additional attachment ** Attachment added: "X log after pressing ENTER - Toshiba Portegé Z930" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/532047/+attachment/3453843/+files/2012-12-05%2018.39.26.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/532047 Title: Plymouth text-mode splash causes X to crash on first run due to shared tty7 Status in X.Org X server: Invalid Status in “plymouth” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Invalid Bug description: Binary package hint: plymouth Lucid adopted the Plymouth graphical splash service that uses the Kernel Mode Setting (KMS) facilities to provide a flicker-free graphical splash during start-up. For older video chipsets and drivers (e.g. intel i815) that *do not* support KMS plymouth falls back to using a text console (using the text plugin). It attaches to tty7 and outputs Linux terminfo control codes to draw a colour progress-bar at the bottom of the display. There is an unfortunate interaction between plymouth and X. X also uses tty7. When the X/GDM log-in screen appears for the first time plymouth is still running. A script triggers a quit message to the plymouth daemon. It seems that plymouth is waiting for either the "2" key or "Enter" key to be pressed, whereupon a SIGQUIT (signal 3) is sent to tty7. This causes both plymouth *and* X to terminate. So, if a password contains "2" or the user logs in by pressing "Enter" after typing their password, the user experience is that X 'crashes' (however, gdb reveals that X receives SIGQUIT). Some stray plymouth control codes can be witnessed on tty7 if X is stopped and tty7 console is on-screen. Upstart (/sbin/init) then restarts gdm (which launches X) and the second session performs correctly. *** A temporary workaround is to disable the plymouth-splash upstart job *** sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth- splash.conf.disabled To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 532047] Re: Plymouth text-mode splash causes X to crash on first run due to shared tty7
I have this problem with a Toshiba Portegé Z930 and Ubuntu 12.04. But I get instead a black screen with a mouse cursor and a console cursor blinking. After pressing 2 or ENTER, lightdm starts again. I leave a "tail -f /var/log/Xorg.0.log" on the tty1 before pressing 2 or ENTER, and then I press it, and I can see the crash log. I'm attaching it. #105 workaround does NOT fix the problem for me. Removing the /etc/init /plymount-splash.conf does, however. ** Attachment added: "Black screen before pressing ENTER - Toshiba Portegé Z930" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/532047/+attachment/3453842/+files/2012-12-05%2018.15.59.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/532047 Title: Plymouth text-mode splash causes X to crash on first run due to shared tty7 Status in X.Org X server: Invalid Status in “plymouth” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Invalid Bug description: Binary package hint: plymouth Lucid adopted the Plymouth graphical splash service that uses the Kernel Mode Setting (KMS) facilities to provide a flicker-free graphical splash during start-up. For older video chipsets and drivers (e.g. intel i815) that *do not* support KMS plymouth falls back to using a text console (using the text plugin). It attaches to tty7 and outputs Linux terminfo control codes to draw a colour progress-bar at the bottom of the display. There is an unfortunate interaction between plymouth and X. X also uses tty7. When the X/GDM log-in screen appears for the first time plymouth is still running. A script triggers a quit message to the plymouth daemon. It seems that plymouth is waiting for either the "2" key or "Enter" key to be pressed, whereupon a SIGQUIT (signal 3) is sent to tty7. This causes both plymouth *and* X to terminate. So, if a password contains "2" or the user logs in by pressing "Enter" after typing their password, the user experience is that X 'crashes' (however, gdb reveals that X receives SIGQUIT). Some stray plymouth control codes can be witnessed on tty7 if X is stopped and tty7 console is on-screen. Upstart (/sbin/init) then restarts gdm (which launches X) and the second session performs correctly. *** A temporary workaround is to disable the plymouth-splash upstart job *** sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth- splash.conf.disabled To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 574960] Re: Usability issue: Loading indication is not visible enough
Yup, I think this is not applicable anymore (resolved) as of Gwibber 3.4.0 -- 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/574960 Title: Usability issue: Loading indication is not visible enough Status in “gwibber” package in Ubuntu: Incomplete Bug description: When Gwibber is loading messages, it will display an empty white window and a spinning circle next to the menu, which is barely invisible, at least using ambiance and ambiance-maverick-beta. I like the approach of Pino, which shows a "Loading..." text centered on the window when loading, which makes it much more user friendly. Older description: On earlier versions of Gwibber there was a "Loading" indication. Now, all we get is a blank pane and the hope that's still doing something in background. It shoud be at least some kind of rolling circle to tell the user "Hey, I'm really doing something, I'm not stalled". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/574960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 697612] Re: Use avatars in addition to colors for accounts selector
The user account icon alongside the service (Twitter, Identi.ca...) icon should be used when available, as every Twitter application out there is doing this and the user will mostly expect it from Gwibber. In addittion, on Gwibber 3.2.0.1, the color is used on the new tweet tooltip, but NOT on the mouseover account icon that popups on every tweet/message. As a result, you'll have two or more identical icons with the same tooltip if you have more than one account with the same provider. Also, you will never know from what account the tweet/message comes from. Should I issue a separate bug? -- 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/697612 Title: Use avatars in addition to colors for accounts selector Status in Gwibber: New Status in “gwibber” package in Ubuntu: Triaged Bug description: Binary package hint: gwibber Gwibber is now a really good tool to manage several social services within a single tool. Something that could improve its usability for people who manage quite of a few of those (e.g. several twitter accounts) would be to show the avatar linked to the account in the icons used to select which account will be used to send a status update. At this time, Gwibber uses the service logo and a user-picked color (completed by a mouse over tooltip) ; instead of a color (or maybe in addition to it?), I think an icon that would combine the service logo and the avatar used for the given account would make it much easier to pick the right account one wants to use for a given update. To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/697612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp