[Desktop-packages] [Bug 1908469] Re: Cannot install .deb packages opened from Firefox
tmp will not work for some applications; any link explaining exactly why/when/how? is it just because of snap - or other things too? -- 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/1908469 Title: Cannot install .deb packages opened from Firefox Status in firefox package in Ubuntu: Confirmed Bug description: Suppose in Firefox you click a link to a .deb package. A dialog named "Opening [filename].deb" opens. If you select "Open with", then the .deb file is downloaded, placed in /tmp/mozilla_[username]0/ directory, then Software Install (as named in the Firefox dialog) is started on that .deb file. Next, Software Install loads and fails with "Failed to install file: not supported". If on the other hand, in Firefox's "Opening [filename].deb" dialog, if I select "Save File" instead, the .deb file ends up in the user's Downloads directory. Software Install works fine with the package there. I don't want to get too much into solutioning or "why". The main point of this bug is that I should not get a weird error just because I selected "Open with" instead of "Save File". This happens with a vanilla install of Ubuntu, with nothing else installed, so the product isn't working in an intuitive way. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 19:54:01 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-12-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
bump. thinkpad x1 5th gen carbon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in pm-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
(PS: all along I thought my headphones had dropped once too often... only now discovered by chance that it's a Ubuntu-related bug.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
bump (Ubuntu 20.04.1 LTS, 5 Nov 2020). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1710421] Re: Keyboard accelerators for window menus aren't implementedbText you copy will automatically show here
On Tue, 11 Aug 2020, 11:51 Daniel van Vugt, <1710...@bugs.launchpad.net> wrote: > ** Tags removed: eoan > > ** Tags added: focal > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1710421 > > Title: > Keyboard accelerators for window menus aren't implemented > > Status in GNOME Shell: > Confirmed > Status in gnome-shell package in Ubuntu: > Confirmed > > Bug description: > Description from duplicate bug 1725706: > > Steps to reproduce: > 1. Install Ubuntu 17.10 > 2. Login to the default Ubuntu session > 3. Open any windowed application such as Nautilus or `gnome-terminal` > 3. Click to show current window settings > 4. Try to set "Always on Top" property with keyboard shortcut () > > Expected results: > * window reacts on and set on top as requested > > Actual results: > * window does not react on > > Notes: > "Always on Top" is just an illustration. Mnemonics for other (Minimize, > Maximize, Move, Resize, Always on Visible Workspace, Move to workspace > down, etc) do not defined and do work too. > > > > Original description below: > > Other desktop systems including Microsoft Windows and Unity have > accelerator keys in the window menu. This is typically accessible via > ALT_Space on any window, then pressing a key to initiate the desired > function. > > Typically Alt_Space can be used to bring up the menu, then use x to > maximise a window, n to minimise a window, etc. GNOME Shell does not > implement these accelerator keys, which seems inconsistent with other > desktops, and internally inconsistent, as other menus in GNOME > applications _do_ have accelerator keys. > > It would be great for people coming to GNOME Shell should be able to > use the familiar keyboard shortcuts they're used to. > > As far as I can test (as far back as 16.04) this has always been the > case. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: gnome-shell 3.24.3-0ubuntu1 > ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 > Uname: Linux 4.11.0-13-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl zcommon znvpair > ApportVersion: 2.20.6-0ubuntu5 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Sat Aug 12 22:49:46 2017 > DisplayManager: gdm3 > InstallationDate: Installed on 2017-08-02 (10 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 > (20170712) > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1710421/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1710421 Title: Keyboard accelerators for window menus aren't implemented Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Description from duplicate bug 1725706: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open any windowed application such as Nautilus or `gnome-terminal` 3. Click to show current window settings 4. Try to set "Always on Top" property with keyboard shortcut () Expected results: * window reacts on and set on top as requested Actual results: * window does not react on Notes: "Always on Top" is just an illustration. Mnemonics for other (Minimize, Maximize, Move, Resize, Always on Visible Workspace, Move to workspace down, etc) do not defined and do work too. Original description below: Other desktop systems including Microsoft Windows and Unity have accelerator keys in the window menu. This is typically accessible via ALT_Space on any window, then pressing a key to initiate the desired function. Typically Alt_Space can be used to bring up the menu, then use x to maximise a window, n to minimise a window, etc. GNOME Shell does not implement these accelerator keys, which seems inconsistent with other desktops, and internally inconsistent, as other menus in GNOME applications _do_ have accelerator keys. It would be great for people coming to GNOME Shell should be able to use the familiar keyboard shortcuts they're used to. As far as I can test (as far back as 16.04) this has always been the case. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Aug 12 22:49:46 2017
[Desktop-packages] [Bug 745608] Re: [915GM] font corruption on Intel GMA900
Years ago I applied the solution described here http://askubuntu.com/a/49941/16023 I'm still on precise (not raring). Lately, the issue's been cropping up more often again. What's the latest consensus on how to resolve this issue in precise ? Anything else worth trying? -- 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/745608 Title: [915GM] font corruption on Intel GMA900 Status in X.org xf86-video-intel: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Debian: Confirmed Bug description: Sometimes getting incomplete drawing of same glyphs of one font on whole screen. In the screenshot you can see the e is drawn incompletely (both english and cyrillic too). The bug is happening frequently and spontaneous on my Asus EEEPC 900. (This issue affects Ubuntu's 10.10 or later. A workaround using the DebugWait parameter is described in comment #40 - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/745608/comments/40 ). [lspci] Nux: lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/745608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 709098] Re: Navigation between side pane and main window is difficult
what about F6 ? -- 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/709098 Title: Navigation between side pane and main window is difficult Status in One Hundred Paper Cuts: Confirmed Status in Nautilus: New Status in “nautilus” package in Ubuntu: Confirmed Bug description: Moving focus between the side pane and the main window using only the keyboard is very difficult. Currently, you have to move focus from the side pane to the main window by first pressing the tab key followed by the down cursor key twice. This would be made far easier if it was simply tab that was needed to move from the said pain to the main window, and tab again to move back. This would mean that the tab would simply move focus between the side pane and main window and back again. It should also be the case the focus is automatically given to the main window, so that the user can immediately be given the opportunity to browse their files/folders in the folder of their choice, and they can use the tab to move back to the side pane. I think it would be a good idea to allow this functionality to work from anywhere within the main window (ie, you don't have to be in the far left row). To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/709098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950160] Re: Unity blocks other programs from binding globally to Super+* (* = any key)
Regarding WORKAROUND 1: maybe I'm doing sth wrong, but I've disabled many settings in CCSM, Launcher's launched via a non-super shortcut; still, I can't get super to work in a custom keyboard shortcut. What could I be doing wrong? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/950160 Title: Unity blocks other programs from binding globally to Super+* (* = any key) Status in Compiz: Fix Committed Status in Compiz 0.9.8 series: In Progress Status in Compiz Core: Confirmed Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “compiz” source package in Precise: Triaged Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “unity” source package in Precise: Triaged Status in “compiz” source package in Quantal: Triaged Status in “gnome-settings-daemon” source package in Quantal: Fix Released Status in “unity” source package in Quantal: In Progress Bug description: WORKAROUND 1: Run CCSM and under Ubuntu Unity Plugin change the key binding for Key to show the launcher to something else (e.g. Super+U). Then log out and in again. As long as no compiz plugin is bound to the single Super key any more, compiz will no longer block other apps from binding to Super+other_keys. WORKAROUND 2: 1. Write a script or figure out the command to do the action you want. 2. Run ccsm. 3. Enable the Commands plugin 4. In the Commands settings, fill in the command line you want and bind it to key Super+P. Now Unity will run your specified command on Super+P, but still handle the Super key as usual. [Precise SRU Justification] [Impact] Any shortcut with Super, Hyper, Meta virtual modifiers does not work [Test Case] Attach an external monitor to the laptop, press Super+P, it should do the video switch as this function is implemented in gnome-settings-daemon. A patch in comment #12 is now accepted upstream and a test package with that patch is available in comment #14. From the test result, the patch at least fixes Unity-2D. [Regression Potential] The patch is accepted upstream and is also cherry-picked in the gnome-3-4 branch of g-s-d git tree. g-s-d version in Precise is 3.4.2. So the risk of regression should be rather low. [Other] I prepare a debdiff in comment #31 for convenience. I hope the patch can be in both Quantal and Precise. ORIGINAL DESCRIPTION: Using : 12.04 Beta 1, updated. and Unity. In 11.10 clicking: - the function key (Fn) + (F1) allowed to switch between the laptop screen and the external monitor. After upgrading to 12.04 this no more works and instead I get an unexpected behavior: see the video. https://www.youtube.com/watch?v=-vEnrV5TwXo System: Dell XPS 15 L502X ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-sso-client 2.99.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 19:18:42 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ubuntu-sso-client UpgradeStatus: Upgraded to precise on 2012-03-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/950160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1105453] Re: gEdit hangs when searching a minimized css file
related to this https://live.gnome.org/Gedit/FAQ ? gedit is very slow and/or crashes when opening files with very long lines. Can you fix it? When designing GtkTextView (the text display widget of gtk+ which gedit uses) the developers had to make a design decision: trading off bad performance and memory use on corner cases like very long lines in exchange for better performance in search operations and full support for UTF-8 text. This is a known limitation of GtkTextView and cannot be fixed. On top of that Pango seems to use a lot of CPU drawing such long lines. This may be fixable, but it isn't easy... Feel free to give it a try. Crashes with long lines are usually due to out-of-memory conditions, but if that's not the case then we would like to know about it. I think I've suffered from the long-line issue a lot, and have used leafpad (and am about to try geany) as a more reliable alternative; don't get me wrong: if gedit were reliably stable and would not become UNUSABLE for certain documents, I'd have zero complaints about it... -- 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/1105453 Title: gEdit hangs when searching a minimized css file Status in “gedit” package in Ubuntu: New Bug description: I tried searching for ps_main using the Search function in gEdit and it just hung on me. Steps to reproduce: 1) start gedit 2) open de supplied css file 3) notice that for a file that's just 217,6kB big, and has 217630 lines, it load a bit slow 4) Use the search function to find ps_main 5) notice gedit hanging up, the program gets darkened due to not responding ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gedit 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Fri Jan 25 22:18:11 2013 InstallationDate: Installed on 2012-12-05 (51 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1105453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1136644] Re: gedit search function is not practical anymore
related to this https://live.gnome.org/Gedit/FAQ ? gedit is very slow and/or crashes when opening files with very long lines. Can you fix it? When designing GtkTextView (the text display widget of gtk+ which gedit uses) the developers had to make a design decision: trading off bad performance and memory use on corner cases like very long lines in exchange for better performance in search operations and full support for UTF-8 text. This is a known limitation of GtkTextView and cannot be fixed. On top of that Pango seems to use a lot of CPU drawing such long lines. This may be fixable, but it isn't easy... Feel free to give it a try. Crashes with long lines are usually due to out-of-memory conditions, but if that's not the case then we would like to know about it. I think I've suffered from the long-line issue a lot, and have used leafpad (and am about to try geany) as a more reliable alternative; don't get me wrong: if gedit were reliably stable and would not become UNUSABLE for certain documents, I'd have zero complaints about it... -- 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/1136644 Title: gedit search function is not practical anymore Status in “gedit” package in Ubuntu: New Bug description: i use gedit a lot, and i find it comfortable in general. the new small search window is extremely impractical. FOCUS PROBLEM: CTRL+F type a search (search of longer strings FAR TOO SLOW) find and now, typing ESC brings one back to the former place! when trying to use CTRL-F again, the search string is replaced by new text. if one wants to stay in the found passage, one must use the mouse/touchpad to click into the text. this is an extremely annoying feature/behavior. i simply would like to have the old search window + its behavior back. i am working very quickly and mostly using shortcuts. gedit now completely interrupts my way of working. additionally, where are the other search functions such as case- sensitive search? additionally, i do not want the search function to slow down so much. for me it is ok to start the search after i have finished typing my search string :-) this new energy-consuming ZEITGEIST-etc-fashion is not good for quick workers with serious amounts of data. best wishes, vollmanr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1136644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 781931] Re: New windows are moved to front but don't take focus
alt-tab still often seems to focus into nirvana... -- 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/781931 Title: New windows are moved to front but don't take focus Status in Compiz: Fix Committed Status in Compiz Core: Confirmed Status in GTK+ GUI Toolkit: Invalid Status in Nautilus: Fix Released Status in Unity: Invalid Status in Unity 2D: Invalid Status in Unity Distro Priority: Fix Committed Status in “compiz” package in Ubuntu: Fix Committed Status in “nautilus” package in Ubuntu: Fix Released Status in “unity-2d” package in Ubuntu: Won't Fix Status in “compiz” source package in Precise: Confirmed Status in “nautilus” source package in Precise: Fix Released Status in “unity-2d” source package in Precise: Won't Fix Bug description: Impact: sometime new dialog doesn't get the focus Test Case for the nautilus SRU: - open gedit, click in the text entry - click on nautilus on the launcher - check if the nautilus dialog got the focus or not Regression potential: nautilus could steal focus when it should not To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/781931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
