[Desktop-packages] [Bug 626553] Re: mouse pointer strange behavior
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/626553 Title: mouse pointer strange behavior Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox This is highly random.when FF runing where ever I put my curser it starts (window or gnome pannel icon) blinking rapidly.Clicks on icons dosent work and if its a terminal window blinkin curser in it shows that it gets selected and de selected rapidly.I get this when firefox running.its gone after few seconds and during this period FF gets gray.. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.8+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Aug 30 06:42:06 2010 FirefoxPackages: firefox 3.6.8+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.8+build1+nobinonly-0ubuntu3 firefox-branding 3.6.8+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100215) ProcEnviron: LANGUAGE=en_GB:en LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/626553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 612182] Re: Clicking the scroll bar scrolls more than one page
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/612182 Title: Clicking the scroll bar scrolls more than one page Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox Open a long page in Firefox. Click anywhere in the bottom part of the page scroll bar (but not on the arrow button). Firefox scrolls down by different amounts at different times. Sometimes it is only one page, but usually it is two or more. The scrolling behavior across the system should be consistent. Firefox should scroll only one page down just like the Gnome apps. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Sun Aug 1 08:19:47 2010 FirefoxPackages: firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1 firefox-gnome-support 3.6.8+build1+nobinonly-0ubuntu0.10.04.1 firefox-branding 3.6.8+build1+nobinonly-0ubuntu0.10.04.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/612182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 845063] Re: can only open pdf once
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/845063 Title: can only open pdf once Status in firefox package in Ubuntu: Expired Bug description: I can open a PDF only once in Firefox, after that see only blank page. Restarting Firefox solves the problem. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 6.0.2+build2+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Thu Sep 8 08:39:03 2011 FirefoxPackages: firefox 6.0.2+build2+nobinonly-0ubuntu0.11.04.1 flashplugin-installer 10.3.183.7ubuntu0.11.04.1 adobe-flashplugin N/A icedtea-plugin 1.1.1-0ubuntu1~11.04.1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/845063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 616201] Re: firefox view picture darken than usual.
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/616201 Title: firefox view picture darken than usual. Status in firefox package in Ubuntu: Expired Bug description: the version i using is ubuntu 10.04 with firefox 3.6.8. the picture or photo inside the firefox appear to be darker than usual color. [IMG]http://img442.imageshack.us/img442/3448/screenshotpu.jpg[/IMG] the left hand side is the photo view by firefox, and the right hand side is the one open by picasa, and it saved from the firefox. is there any way to solve tis problem? thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/616201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 646704] Re: I have firefox preference to show blank page on startup, but it often tries to reload the previous page - especially if it wasn't closed down properly.
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/646704 Title: I have firefox preference to show blank page on startup, but it often tries to reload the previous page - especially if it wasn't closed down properly. Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox I have firefox preference to show blank page on startup, but it often tries to reload the previous page - especially if it wasn't closed down properly. I am using vers 3.6.9 of firefox but I'm sure it happened to previous versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/646704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962321] Re: All tabs froze and never recovered.
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/962321 Title: All tabs froze and never recovered. Status in firefox package in Ubuntu: Expired Bug description: All tabs froze and never recovered. When I restarted firefox, previous tabs were not recovered. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: firefox 11.0+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1495 F pulseaudio /dev/snd/controlC1: user 1495 F pulseaudio BuildID: 20120310010446 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfea78000 irq 44' Mixer name : 'VIA VT1708B 8-Ch' Components : 'HDA:1106e721,104382ea,00100100' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'Camera'/'Sonix Technology Co., Ltd. USB 2.0 Camera at usb-:00:1d.7-2, high speed' Mixer name : 'USB Mixer' Components : 'USB0c45:62f1' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 512 Mono: Capture 0 [0%] [0.00dB] [on] Channel: release Date: Thu Mar 22 16:21:22 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.50 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: PATH=(custom, no username) LANG=en_IN SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=11.0/20120310010446 (Running) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to oneiric on 2012-01-12 (69 days ago) dmi.bios.date: 01/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0305 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-CM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0305:bd01/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-CM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/962321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 903600] Re: Feedback plugin update notification popping foreground firefox window
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
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/903600
Title:
Feedback plugin update notification popping foreground firefox window
Status in firefox package in Ubuntu:
Expired
Bug description:
When feedback plugin for firefox asking for update, it brings up
firefox window to foreground, disturbing work with other applications.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 9.0~b5+build1-0ubuntu1
Uname: Linux 3.2.0-rc4 i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.90-0ubuntu1
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: amarao 1557 F pulseaudio
BuildID: 20111209134252
CRDA:
country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9152 irq 44'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:14f1506e,17aa21da,0010
HDA:80862805,80860101,0010'
Controls : 23
Simple ctrls : 8
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Channel: beta
Date: Tue Dec 13 12:27:02 2011
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
default via 192.168.40.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.40.0/24 dev wlan0 proto kernel scope link src 192.168.40.44
metric 2
ProcEnviron:
LANGUAGE=en
PATH=(custom, no user)
LANG=ru_RU.UTF-8
LC_MESSAGES=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=9.0/20111209134252
RfKill:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET49WW (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4290RB3
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:bvr8DET49WW(1.19):bd07/01/2011:svnLENOVO:pn4290RB3:pvrThinkPadX220:rvnLENOVO:rn4290RB3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4290RB3
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/903600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 653167] Re: Firefox awsomebar stops working after suspend/resume
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/653167 Title: Firefox awsomebar stops working after suspend/resume Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox After a suspend resume cycle firefox's awsomebar stops working. Bug present in both 10.04 and 10.10. How to reproduce: Make sure you have visited a few sites so firefox has some browsing history 1. Start firefox 2. Click on 0/1 in the Indicator applet and choose suspend (leave the firefox window open maximized) 3. Resume 4. Start typing the address of some site you have in your browser history At this point firefox does not suggest anything. Switching to another application and back to firefox fixes the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/653167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 573597] Re: freeze in adress bar search
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/573597 Title: freeze in adress bar search Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox when typing adress in adress bar, freeze after every character ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 Uname: Linux 2.6.34-999-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun May 2 13:58:13 2010 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 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) ProcEnviron: LANGUAGE=ru:ru_UA:en LANG=ru_UA.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/573597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 818595] Re: Firefox 5.0 shockwave plugin causes missing and non functional file browsing
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/818595 Title: Firefox 5.0 shockwave plugin causes missing and non functional file browsing Status in Mozilla Firefox: Incomplete Status in firefox package in Ubuntu: Expired Bug description: When any web feature asks to browse to a file location and the file navigation window comes up, it is only white page with black text. Example: You want to attach a file in webmail aka yahoo.com (select compose/attach/browse) the window comes up but only white text with black backround and the navigation does not work and what should be the OK button makes the window crash. No buttons,button borders, no colors, and no highlighting of selected files. Same bug for all add files features when initiated from the firefox browser: Ebay add images Facebook add images Ubuntu forums add images NOW ! after lots of playing around I found that if I disable the shockwave plugin in firefox 5.0 then the file navigation features are back to normal and function as they should. But what to do with shockwave ? Please advise Thanks ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Jul 30 13:13:51 2011 FirefoxPackages: firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2 flashplugin-installer 10.3.181.34ubuntu0.11.04.1 adobe-flashplugin N/A icedtea-plugin 1.1.1-0ubuntu1~11.04.1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/818595/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1091189] Re: firefox scroll bug confused with
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1091189 Title: firefox scroll bug confused with Status in firefox package in Ubuntu: Expired Bug description: Open any webpage whose contents are taller than the firefox window. Good in-house examples are bug reports on launchpad. When the page has finished loading, type on the keypad, type on the keypad, type again, and type again. The scrolling is different the second time. The page scrolls to the bottom correctly when typing , but typing the first time makes the page scroll all the way to the top, instead of scrolling just one line up, i.e. works like . But after that, typing and then the up-scrolling works correctly with the page scrolling up by one line. This is a quite annoying bug because it is a common usecase to need to scroll to the bottom of web forums and bug trackers and then scroll up a few lines to see the previous comment. This happens on every scrollable webpage, without any addons, in safe mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1091189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1451851] Re: OK button in certificate manager's trust setting dialog is permanently greyed out
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1451851 Title: OK button in certificate manager's trust setting dialog is permanently greyed out Status in firefox package in Ubuntu: Expired Bug description: step 1: download root.crt and class3.crt from https://www.cacert.org/index.php?id=3 step 2: import in certificate manager / tab "certificate authorities" step 3: scroll down to "Root CA" which now contains two modules "CAcert Class 3 Root" and "CA Cert Signing Authority" step 4: select one of these modules and click "edit trust..." Expected behaviour: I can mark one or more options and set the new trust settings for that certificate by clicking "OK". Problem: "OK" button is dimmed. Affected system: Lenovo Thinkpad SL510 / Ubuntu 14.04 LTS Master Password is set and activated. (works without problems on a different system: OS X 10.8.5 / Firefox 37.0.2) The user (not me) hasn't run certutil yet but apart from that the dialog should work in the first place. Also I wonder if this can be a read/write access problem with the downloaded/imported *.crt files but not sure where to look. Thanks, Carl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1451851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1598420] Re: Switch account and there is not possible to type in location bar in Firefox anymore
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1598420 Title: Switch account and there is not possible to type in location bar in Firefox anymore Status in firefox package in Ubuntu: Expired Bug description: On Ubuntu 16.04 Desktop 32-bit. 1. Login into Ubuntu with normal user. 2. Everything works fine also in Firefox without a problem. 3. Wait for few minutes that screen gets locked or press Super+L to lock a screen. 4. Now on log on screen select another user and login. 5. Start Firefox (default browser installed when Ubuntu is installed). 6. Click in location bar and try to type something in it. It looks like keyboard does not work. This is a problem! With mouse selecting some saved link from bookmarks and then try to use keyboard, Home/End/PageUp/PageDown works without a problem, but typing letters in location or search box can not be performed. Looks like a keyboard problem. But open Gedit, Terminal or any other application and typing letters works without a problem. Work-around for this problem: 1. Close Firefox. 2. Open Terminal and type in: who -u To get the pid of logged in user. 3. Kill process: sudo kill -9 4. Start Firefox and now typing in location and search box works fine. I can reproduce this problem every time! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 47.0+build3-0ubuntu0.16.04.1 [modified: usr/share/applications/firefox.desktop] ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 7434 F pulseaudio BuildID: 20160606113900 Channel: Unavailable CurrentDesktop: Unity Date: Sat Jul 2 13:35:33 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-06-03 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) IpRoute: default via 192.168.64.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.64.0/24 dev wlp3s0 proto kernel scope link src 192.168.64.102 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js [Profile]/extensions/https-everywh...@eff.org/defaults/preferences/preferences.js Profiles: Profile0 (Default) - LastVersion=47.0/20160606113900 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 79ET62WW (1.07 ) dmi.board.name: 1951F5G 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:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1951F5G dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1598420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787194] Re: On inserting page numbers, instructions are disobeyed
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1787194 Title: On inserting page numbers, instructions are disobeyed Status in libreoffice package in Ubuntu: Expired Bug description: 1- In UBUNTU 18.04,inserting page numbers does not work. I selected: insert- field - more fields, then selected "Page" in the "Type" list under the document tab, following I selected "next page" in the select list. Then, whatever I select from the format list I Just get the last selection printed in the field of page number The last selection was "next page", thus I got these words printed but no page numbers. I don't receive error messages. I still have Windows10 , on my lab but I rarely use it. I an stopping windows update. Meanwhile, I get UBUNTU regular updates and currently my UBUNTU soft ware is up to date. 2- In printing any document, I must put the printer off first choose what is to print and click OK then starting the printer. In the meantime, only one job is printed after all this. Normally the first clicked job. I have "Printer" and "Printer settings" software. Here also I don't receive error messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1787194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787925] Re: gnome-shell crashed with SIGABRT in meta_bug()
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1787925 Title: gnome-shell crashed with SIGABRT in meta_bug() Status in gnome-shell package in Ubuntu: Expired Bug description: I have not much to say. I just happened without doing anything special. I am working with the virtualbox GUI over SSH and x-forwarding. That's all. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: blackmagic_io blackmagic nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Aug 20 12:42:56 2018 DisplayManager: gdm3 InstallationDate: Installed on 2014-04-18 (1584 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: gnome-shell UpgradeStatus: Upgraded to xenial on 2018-06-09 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739468] Re: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered
gnome-shell[11642]: [AppIndicatorSupport-WARN] Item :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1 is already registered gnome-shell[11642]: [AppIndicatorSupport-WARN] Attempting to re-register :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1; resetting instead is repeating every minute in syslog. Description:Ubuntu 18.04.1 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1739468 Title: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Bug description: The following message is continuously logged to /var/log/syslog (every few seconds): Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Attempting to re-register :1.51/org/ayatana/NotificationItem/multiload; resetting instead Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered It's hard to find anything in syslog because thousands of these messages intermingle with everything else ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 20 10:28:49 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-13 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1739468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1074286] Re: system-config-printer/applet.py should be implemented with a binary executable
Setting to Triaged/Low as requested. ** Changed in: system-config-printer (Ubuntu) Importance: Undecided => Low ** Changed in: system-config-printer (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1074286 Title: system-config-printer/applet.py should be implemented with a binary executable Status in system-config-printer package in Ubuntu: Triaged Bug description: After loging into XFCE environment, I see with "top" that /usr/share /system-config-printer/applet.py consumes 22MB of physical memory, just behind X. Most of the time, the printer applet does nothing and thus wastes memory. I think that this applet should be implemented with a compiler which create a binary executable instead of writing a python script or python byte code which will never reach the performances of a binary executable (speed and memory). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: system-config-printer-gnome 1.3.11+20120807-0ubuntu10 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CurrentDmesg: [ 913.672003] mtrr: no MTRR for e000,100 found Date: Fri Nov 2 10:32:45 2012 InstallationDate: Installed on 2012-10-20 (12 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: innotek GmbH VirtualBox MarkForUpload: True PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=cd43b074-5f0e-46e5-8362-13424056d921 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: Error: [Errno 13] Permission non accordée: '/var/log/cups/error_log' CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Dell Inc. Latitude E6430 Package: system-config-printer (not installed) Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-137-generic root=UUID=19fbf7a9-ba26-43ce-9f73-2ffc42922043 ro quiet ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Tags: xenial Uname: Linux 4.4.0-137-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-09-02 (398 days ago) UserGroups: audio cdrom fuse plugdev sudo vboxusers video _MarkForUpload: True dmi.bios.date: 10/08/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 08R94K dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn08R94K:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1074286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1773697 Title: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Bug report has been generated on a partially working configuration. That allows ubuntu-bug to do more work. USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly stopped working again on newer kernels. The bug report has been generated on the latest working mainline kernel 4.15.7. All newer kernels have some usb quirks in place, which should fix the playback sample rates to 48 kHz. The quirk seems not to be working correctly and hinder the audio system to recognize the USB-device as a sound device. The Headphones work on kernels before 4,15.7 when manually configuring pulseaudio to a default samplerate of 48 kHz. PX Headphones are on the newest firmware level. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.15.7-041507-lowlatency x86_64 AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', '--no-upload'] failed with exit code 1: mktemp: failed to create directory via template '/tmp/zsh-1000/alsa-info.XX': No such file or directory ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio CurrentDesktop: GNOME Date: Sun May 27 22:21:53 2018 InstallationDate: Installed on 2016-02-05 (841 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: PX USB - PX USB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dshr 2729 F pulseaudio /dev/snd/controlC1: dshr 2729 F pulseaudio /dev/snd/controlC0: dshr 2729 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [USB-Audio - PX USB, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago) dmi.bios.date: 06/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET33W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS00Q00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS00Q00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dshr 3423 F pulseaudio /dev/snd/pcmC0D0c: dshr 3423 F...m pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-02-07 (248 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128) MachineType: LENOVO 4291QQ1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET51WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291QQ1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information
[Desktop-packages] [Bug 1799008] Re: [SRU] Update logo for cosmic
** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1799008 Title: [SRU] Update logo for cosmic Status in unity-control-center package in Ubuntu: Confirmed Bug description: [Impact] System-Settings -> Details -> Overview panel in unity-control-center should show the correct release version i.e Ubuntu 18.10 [Test Case] System-Settings -> Details -> Overview panel in unity-control-center still shows Ubuntu 18.04 LTS [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1799008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797860] Re: Language selection installs too many packages
On 2018-10-17 08:14, Didier Roche wrote: > When you are telling that you select French, or English, and so, all > dialects should be installed for them, why do we have that separation > in different packages though? Shouldn't we only have one "English", > "French", … package? I now understand that we have been talking past each other wrt to the definition of "language packs". With language packs I usually refer to the Ubuntu specific language packs which provide translations from LP. So for English, for instance, there is one set of language packs: language-pack-en-base language-pack-en language-pack-gnome-en-base language-pack-gnome-en Such a set includes all the dialects of a language if there are more than one. Also, the "Installed Languages" window in Language Support checks for those very packages when determining whether a language is installed or not. The other language related packages (spell checking, firefox translations, input methods...) I usually call "language support". Some of those are indeed split into dialects, which mostly is the result of how Debian organizes it in e.g. libreoffice-dictionaries. > I don't understand the difference between: > $ locale -a | grep ^fr > fr_BE.utf8 > fr_CA.utf8 > fr_CH.utf8 > fr_FR.utf8 > fr_LU.utf8 > > and the script outputting only fr/fr_FR/fr_CA. There is no > translation available in /usr/share/locale for fr_BE for instance? For me there isn't. If some fr_BE translation would end up in /usr/share/locale due to some universe package, the script would include fr_BE too in the output. The output is dynamically generated. > How this does differ fr_BE, from fr_FR, as it's the same currency, > time format and no specific string (as no separate langpack) and so > on? They probably don't differ much. When you install French, all the French UTF-8 locales provided by glibc are installed. There is no mechanism in place to determine their usefulness. Please note that the language-options script serves the purpose of providing a list of languages only, i.e. it let's the user select the display language. That should be distinguished from selecting the locale for regional formats. For the latter purpose the user is offered an option list consisting of all the generated UTF-8 locales. > I really think that if we decide to always ship all variants (as the > script requires right now), That script isn't the center of it. Its only purpose is to provide a list of options for selecting the display language which consists of the installed translations. So again, it's the "language packs" (se "my" definition above) which makes it sensible (IMHO) to ship all language support variants. It may be worth mentioning that many cycles ago, the Language Support GUI had the ability to distinguish between translations, spell checking, writing aids etc., but that was dropped. I think you'd need to install Lucid to check out what that looked like. :) > it should be one single package: easier > maintenance, list and logic. Are you talking about creating meta packages to pull the language support instead of what's currently in the seed and in language- selector's pkg_depends? If so, I can see the advantage with being able to maintain them in one place. Possibly it should be limited to those languages which are on the ISO. On the downside I see that the current setup with regexes sometimes allows the inclusion of new dictionaries without any action. > On 1.: on the contrary, if we go to install all dialects selecting a > given language, I would rather packs them all in a single (well, > single as "per type", keeping dict, libreoffice and such separated) > package. As we require them to be installed on the system anyway, > this doesn't make any difference for the user, but ease our side. Apparently I misunderstood your intention in my previous comments. I think it should be done via meta packages, in that case. For instance, libreoffice-dictionaries is currently synced with Debian. We don't want to create an Ubuntu/Debian delta with some other way to build the binaries, do we? > 1.5: we can debug that later on, but it seems we want to have "fr" > anyway as we have "en", correct? No. "en" is a special case, an exception. It actually represents the bar in the Language Support GUI which separates the languages included in the LANGUAGE environment variable from other installed languages. It should probably better be dropped from the output, but I haven't found the time/motivation to do that. So let's disregard that "en" item when talking about other languages. In practice, and from a user perspective, selecting "en" is equivalent to selecting "en_US". > Or we want people to specifically > select, like fr_BE (to have the specifics for this locale), but still > install all langpaks without having "fr" listed. That's how it currently works. I think it makes sense. (Well, for languages without alternative dialects present, like German or Swedish, the list only shows "de"
[Desktop-packages] [Bug 1799008] Re: [SRU] Update logo for cosmic
** Branch linked: lp:~khurshid-alam/unity-control-center/update-logo- for-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1799008 Title: [SRU] Update logo for cosmic Status in unity-control-center package in Ubuntu: New Bug description: [Impact] System-Settings -> Details -> Overview panel in unity-control-center should show the correct release version i.e Ubuntu 18.10 [Test Case] System-Settings -> Details -> Overview panel in unity-control-center still shows Ubuntu 18.04 LTS [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1799008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
Debian's xfce4-session package only recommends light-locker, so my suggestion in comment #26 would be an acceptable solution. -- 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/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799007] [NEW] no sound after 18.10 upgrade
Public bug reported: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799007 Title: no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799007] Re: no sound after 18.10 upgrade
other report in the wild: https://askubuntu.com/questions/1085176/sound-
device-lost-after-update-to-18-10
note that their debugging steps don't even work for me, running pacmd
just gets a complaint that the pulse daemon isn't running, even though
it looks like systemd intentionally started it in non-daemon mode:
```
$ pacmd list-cards
No PulseAudio daemon running, or not running as session daemon.
$ pstree
[...]
|-systemd-+-(sd-pam)
| |-at-spi-bus-laun-+-dbus-daemon
| | `-3*[{at-spi-bus-laun}]
| |-dbus-daemon
| |-dconf-service---2*[{dconf-service}]
| |-evolution-addre---5*[{evolution-addre}]
| |-evolution-calen---9*[{evolution-calen}]
| |-evolution-sourc---3*[{evolution-sourc}]
| |-gnome-screensav---3*[{gnome-screensav}]
| |-gnome-shell-cal---5*[{gnome-shell-cal}]
| |-goa-daemon---3*[{goa-daemon}]
| |-goa-identity-se---3*[{goa-identity-se}]
| |-gvfs-afc-volume---3*[{gvfs-afc-volume}]
| |-gvfs-goa-volume---2*[{gvfs-goa-volume}]
| |-gvfs-gphoto2-vo---2*[{gvfs-gphoto2-vo}]
| |-gvfs-mtp-volume---2*[{gvfs-mtp-volume}]
| |-gvfs-udisks2-vo---2*[{gvfs-udisks2-vo}]
| |-gvfsd-+-gvfsd-trash---2*[{gvfsd-trash}]
| | `-2*[{gvfsd}]
| |-gvfsd-fuse---5*[{gvfsd-fuse}]
| |-gvfsd-metadata---2*[{gvfsd-metadata}]
| |-pulseaudio---{pulseaudio}
[...]
```
--
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/1799007
Title:
no sound after 18.10 upgrade
Status in pulseaudio package in Ubuntu:
New
Bug description:
After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
works, it no longer shows any of the audio output devices, not even
the builtin HDMI which usually always shows.
Not sure what happened, but this is a major regression and needs to be
fixed. Note that this isn't the same as the bug with Timidity taking
exclusive soundcard access
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as
I don't have any timidity packages installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1492430] Re: [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound at all
*** This bug is a duplicate of bug 1723150 *** https://bugs.launchpad.net/bugs/1723150 ** This bug has been marked a duplicate of bug 1723150 [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones 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/1492430 Title: [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Description: Ubuntu 15.04 Release: 15.04 This is a 5.1 surround sound set up. No output from any speaker. Sound settings configuration doesn't show proper options for this card - no channel info except for analog stereo and S/PDIF outputs where I would expect to see information on Front/Rear/Center speaker outputs. Output from aplay -l: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: CA0132 Digital [CA0132 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 lspci output: 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05) Subsystem: Dell Device 064c Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel -- 03:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) Subsystem: NVIDIA Corporation Device 1131 Physical Slot: 6 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Output from alsa-info.sh can be found at http://www.alsa-project.org/db/?f=b64f2a2d9279d19e6a0967202595956db577 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-26.28-lowlatency 3.19.8-ckt4 Uname: Linux 3.19.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: keith 1905 F pulseaudio /dev/snd/controlC1: keith 1905 F pulseaudio CurrentDesktop: XFCE Date: Fri Sep 4 14:24:12 2015 InstallationDate: Installed on 2015-09-01 (3 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) 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: keith 1905 F pulseaudio /dev/snd/controlC1: keith 1905 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2015 dmi.bios.vendor: Alienware dmi.bios.version: A03 dmi.board.name: 0XJKKD dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvrA03:bd07/13/2015:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn0XJKKD:rvrA01:cvnAlienware:ct3:cvr: dmi.product.name: Alienware Area-51 R2 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1492430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
note: I'm seeing this issue even though I don't have any timidity packages installed. so I've opened another report to track that base issue: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714 -- 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/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723150] Re: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume
Also affects upstream Debian 10/Buster (4.18.0-2-amd64) -- 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/1723150 Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume Status in alsa-driver package in Ubuntu: Confirmed Bug description: The sound is barely heard in Ubuntu 16.0 from the green front headphone jack. In a dual boot setup with Windows, on Windows, the sound is perfect. Standard solutions found across forums on the Internet do not seem to help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aserov 1843 F pulseaudio /dev/snd/controlC1: aserov 1843 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 12 17:04:24 2017 InstallationDate: Installed on 2017-09-29 (12 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2016 dmi.bios.vendor: Alienware dmi.bios.version: A10 dmi.board.name: 09G12C dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvrA10:bd10/11/2016:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn09G12C:rvrA00:cvnAlienware:ct3:cvr: dmi.product.name: Alienware Area-51 R2 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1723150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723150] Re: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1723150 Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume Status in alsa-driver package in Ubuntu: Confirmed Bug description: The sound is barely heard in Ubuntu 16.0 from the green front headphone jack. In a dual boot setup with Windows, on Windows, the sound is perfect. Standard solutions found across forums on the Internet do not seem to help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aserov 1843 F pulseaudio /dev/snd/controlC1: aserov 1843 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 12 17:04:24 2017 InstallationDate: Installed on 2017-09-29 (12 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2016 dmi.bios.vendor: Alienware dmi.bios.version: A10 dmi.board.name: 09G12C dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvrA10:bd10/11/2016:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn09G12C:rvrA00:cvnAlienware:ct3:cvr: dmi.product.name: Alienware Area-51 R2 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1723150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
** Also affects: xfce4-session (Ubuntu) Importance: Undecided Status: New -- 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/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799008] [NEW] [SRU] Update logo for cosmic
Public bug reported: [Impact] System-Settings -> Details -> Overview panel in unity-control-center should show the correct release version i.e Ubuntu 18.10 [Test Case] System-Settings -> Details -> Overview panel in unity-control-center still shows Ubuntu 18.04 LTS [Regression Potential] None. ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: verification-needed-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1799008 Title: [SRU] Update logo for cosmic Status in unity-control-center package in Ubuntu: New Bug description: [Impact] System-Settings -> Details -> Overview panel in unity-control-center should show the correct release version i.e Ubuntu 18.10 [Test Case] System-Settings -> Details -> Overview panel in unity-control-center still shows Ubuntu 18.04 LTS [Regression Potential] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1799008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799001] [NEW] Theming does not work on LXQt
Public bug reported: [Impact] Without this change, LibreOffice does not correctly use the Breeze theme, which is needed for consistency with the rest of the Lubuntu, LXQt-based desktop. At times, it is even hard to use because of the inconsistent theming which can hide buttons at times. [Test Case] Update to the version of LibreOffice with this patch and open it on a Lubuntu 18.10 installation. It should use the Breeze theming rather than the stock GTK theming on startup. [Regression Potential] Little to none. If for some reason the criteria that is used to check for the LXQt desktop no longer works, which is unlikely in a stable release, this will no longer work. [Other Info] I submitted these upstream (as my first patches \o/): https://gerrit.libreoffice.org/61641 https://gerrit.libreoffice.org/61751 ** Affects: libreoffice (Ubuntu) Importance: Medium Assignee: Simon Quigley (tsimonq2) Status: In Progress ** Affects: libreoffice (Ubuntu Cosmic) Importance: Medium Assignee: Simon Quigley (tsimonq2) Status: In Progress ** Also affects: libreoffice (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Cosmic) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: libreoffice (Ubuntu Cosmic) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1799001 Title: Theming does not work on LXQt Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Cosmic: In Progress Bug description: [Impact] Without this change, LibreOffice does not correctly use the Breeze theme, which is needed for consistency with the rest of the Lubuntu, LXQt-based desktop. At times, it is even hard to use because of the inconsistent theming which can hide buttons at times. [Test Case] Update to the version of LibreOffice with this patch and open it on a Lubuntu 18.10 installation. It should use the Breeze theming rather than the stock GTK theming on startup. [Regression Potential] Little to none. If for some reason the criteria that is used to check for the LXQt desktop no longer works, which is unlikely in a stable release, this will no longer work. [Other Info] I submitted these upstream (as my first patches \o/): https://gerrit.libreoffice.org/61641 https://gerrit.libreoffice.org/61751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1023161] Re: Segfault cycling SANE handle
Thanks for closing the ticket, Jeffrey. Have a great day! :) G -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1023161 Title: Segfault cycling SANE handle Status in HPLIP: Incomplete Status in hplip package in Ubuntu: Fix Released Bug description: The ADF on my HP Deskjet 8500 only ejects the last page if the SANE handle is closed, so I have to cycle it as part of the scan process. This works once, but the second time, HPLIP segfaults. The attached example c code demonstrates the problem. Compile with: gcc hplip_segfault.c -o hplip_segfault -lsane Then run with: ./hplip_segfault To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1023161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798999] [NEW] firefox windows are black in Ubuntu 18.10
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.10 Release:18.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center firefox: Installed: 63.0+build1-0ubuntu1 Candidate: 63.0+build1-0ubuntu1 Version table: *** 63.0+build1-0ubuntu1 500 500 http://ubuntu.osuosl.org/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Normal web browsing experience 4) What happened instead Graphical elements are black. After upgrading to 18.10, firefox graphical elements (window contents, context menus) are black. The only exception is a small rectangle in the upper left corner. Right-clicking within the window creates a context menu, which I am able to verify by observing a new black rectangle of the correct width that can be made to occlude the task bar by initiating it at a suitable starting position. If I launch firefox from a terminal then I get messages like the following: code [GFX1-]: Failed to lock new back buffer. [Parent 25238, Main Thread] WARNING: failed to open shm: Permission denied: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/base/shared_memory_posix.cc, line 129 /code This occurs regardless of which desktop environment I use. Other browsers are working fine. I'm guessing the problem is related to the reported problem accessing shm. However, for the sake of completeness, I am using an AMD gpu with standard driver: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Summary changed: - irefox windows are black in Ubuntu 18.10 + firefox windows are black in Ubuntu 18.10 -- 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/1798999 Title: firefox windows are black in Ubuntu 18.10 Status in firefox package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.10 Release:18.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center firefox: Installed: 63.0+build1-0ubuntu1 Candidate: 63.0+build1-0ubuntu1 Version table: *** 63.0+build1-0ubuntu1 500 500 http://ubuntu.osuosl.org/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Normal web browsing experience 4) What happened instead Graphical elements are black. After upgrading to 18.10, firefox graphical elements (window contents, context menus) are black. The only exception is a small rectangle in the upper left corner. Right-clicking within the window creates a context menu, which I am able to verify by observing a new black rectangle of the correct width that can be made to occlude the task bar by initiating it at a suitable starting position. If I launch firefox from a terminal then I get messages like the following: code [GFX1-]: Failed to lock new back buffer. [Parent 25238, Main Thread] WARNING: failed to open shm: Permission denied: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/base/shared_memory_posix.cc, line 129 /code This occurs regardless of which desktop environment I use. Other browsers are working fine. I'm guessing the problem is related to the reported problem accessing shm. However, for the sake of completeness, I am using an AMD gpu with standard driver: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762588] Re: thunderbird 52.6.0/18.04 beta compact folder broken
Hi Nataraj, For the ease of the programmers, I will add a summery here to complete the bug report. Please feel free to add any corrections. Also, do you mind if I update the title of the bug report to: “thunderbird 52.9.1/18.04 compact folder broken for IMAP Dovecot” Thanks G --- SUMMARY: Ubuntu version: Ubuntu 18.04 thunderbird 1:52.9.1+build3-0ubuntu0.18.04.1 dovecot-1.0.7-9.el5_11.4 Problem is reproducable by the reporter. Steps to reproduce: 1. In Ubuntu 18.04 2. In Thunderbird, in account connected to an IMAP server running Dovecot 2. right click on one folder in the folder list 3. no option available to compact the folder 4. In Ubuntu 14.04 5. In Thunderbird, in account connected to an IMAP server running Dovecot 6. right click on one folder in the folder list 7. compact folder option is available Actual behaviour: compact folder option missing in Ubuntu 18.04 in same version of Thunderbird. Expected behaviour: compact folder option should be available for folders. Additional notes: Only occurs with an IMAP server running Dovecot. Issue not evident on Gmail IMAP. --- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1762588 Title: thunderbird 52.6.0/18.04 beta compact folder broken Status in thunderbird package in Ubuntu: New Bug description: Under Thunderbird 52.6.0/Ubuntu 18.04 latest beta, when I connect to an IMAP server running Dovecot dovecot-1.0.7-9.el5_11.4 the compact command is missing from the individual folder menus. Works fine when I connect to Gmail's IMAP server. Thunderbird 52.7.0 under Ubuntu 14.04 does not have this issue. I notice that the version of Thunderbird under 18.04 is actually older than the version under 14.04. I sugguest an update to a more recent and stable release of Thunderbird before the final release date. Thank You, Nataraj --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nataraj1594 F pulseaudio BuildID: 20180710084133 Channel: Unavailable CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-24 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424) IpRoute: default via 10.1.2.1 dev ens3 proto dhcp metric 100 10.1.2.0/24 dev ens3 proto kernel scope link src 10.1.2.6 metric 100 169.254.0.0/16 dev ens3 scope link metric 1000 IwConfig: lono wireless extensions. ens3 no wireless extensions. Locales: extensions.sqlite corrupt or missing Package: thunderbird 1:52.9.1+build3-0ubuntu0.18.04.1 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Prefs: extensions.lastAppVersion: "52.9.1" (prefs.js) network.cookie.prefsMigrated: true (prefs.js) network.predictor.cleaned-up: true (prefs.js) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710084133 (In use) RfKill: RunningIncompatibleAddons: False Tags: bionic Themes: extensions.sqlite corrupt or missing Uname: Linux 4.15.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1762588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Still no sound, even on Ubuntu 18.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798996] Re: Cannot use it at all...
looks like .deb is bad too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1798996 Title: Cannot use it at all... Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: $ gnome-system-monitor cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied And it does not start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798996] Re: Cannot use it at all...
the deb can be started as root, be previously it would work as non-root too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1798996 Title: Cannot use it at all... Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: $ gnome-system-monitor cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied And it does not start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798996] [NEW] Cannot use it at all...
Public bug reported: $ gnome-system-monitor cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied And it does not start at all. ** Affects: gnome-system-monitor (Ubuntu) Importance: Critical Status: Confirmed ** Tags: regression-release ** Summary changed: - Cannot use it as a snap + Cannot use it at all... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1798996 Title: Cannot use it at all... Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: $ gnome-system-monitor cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied And it does not start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785550] Re: Huge memory usage when changing background
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) 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/1785550 Title: Huge memory usage when changing background Status in gnome-control-center package in Ubuntu: Confirmed Bug description: When I open "change background" window in Settings, RAM usage of gnome-control-center goes over 2 gb. In practice I can't change background since gnome-control-center fills all memory, freezing the system. In general, system will freeze without return every time a program fills the memory faster than the system moving memory to swap. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.28.2-0ubuntu1 Uname: Linux 4.18.0-999-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 6 07:32:28 2018 InstallationDate: Installed on 2017-01-12 (570 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to cosmic on 2018-07-24 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1785550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762588] Re: thunderbird 52.6.0/18.04 beta compact folder broken
My apologies, Nataraj. That was my mistake, leaving it at incomplete status when you had replied. Thanks, Paul, for changing the status back to new. G -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1762588 Title: thunderbird 52.6.0/18.04 beta compact folder broken Status in thunderbird package in Ubuntu: New Bug description: Under Thunderbird 52.6.0/Ubuntu 18.04 latest beta, when I connect to an IMAP server running Dovecot dovecot-1.0.7-9.el5_11.4 the compact command is missing from the individual folder menus. Works fine when I connect to Gmail's IMAP server. Thunderbird 52.7.0 under Ubuntu 14.04 does not have this issue. I notice that the version of Thunderbird under 18.04 is actually older than the version under 14.04. I sugguest an update to a more recent and stable release of Thunderbird before the final release date. Thank You, Nataraj --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nataraj1594 F pulseaudio BuildID: 20180710084133 Channel: Unavailable CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-24 (82 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424) IpRoute: default via 10.1.2.1 dev ens3 proto dhcp metric 100 10.1.2.0/24 dev ens3 proto kernel scope link src 10.1.2.6 metric 100 169.254.0.0/16 dev ens3 scope link metric 1000 IwConfig: lono wireless extensions. ens3 no wireless extensions. Locales: extensions.sqlite corrupt or missing Package: thunderbird 1:52.9.1+build3-0ubuntu0.18.04.1 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Prefs: extensions.lastAppVersion: "52.9.1" (prefs.js) network.cookie.prefsMigrated: true (prefs.js) network.predictor.cleaned-up: true (prefs.js) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Profiles: Profile0 (Default) - LastVersion=52.9.1/20180710084133 (In use) RfKill: RunningIncompatibleAddons: False Tags: bionic Themes: extensions.sqlite corrupt or missing Uname: Linux 4.15.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1762588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798988] Re: Software App back button doesn't work after closing and reopening
** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798988 Title: Software App back button doesn't work after closing and reopening Status in Ubuntu Budgie: New Status in gnome-software package in Ubuntu: New Bug description: Distro: Ubuntu budgie 18.10 64 bit freshly installed distro How to recreate issue? Just choose one "app" (it doesn't matter if it's installed or not) close Software and reopen it. After that the Software will show you the exact page where you left it, you can install the displayed app or remove it), but you cannot return to the main page. My temporary Workaround solution: using xkill will force close the window and after reopening the issue disapears, however if i would simply close again and reopen it, the issue would reappear again. I didn't have this issue with previous version 18.04.1 LTS 64 bit Let me know if more input needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1798988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798984] [NEW] Yaru theme installed but not enabled by default nor available after upgrade to Cosmic
Public bug reported: I have recently upgraded from 18.04 LTS to 18.10, but the Yaru theme is not enabled by default nor available to choose in GNOME Tweaks, even though apt says it is already installed. I had the communitheme snap installed when I was using 18.04 LTS, but it stopped working after the upgrade. $ lsb_release -rd Description:Ubuntu 18.10 Release:18.10 $ apt-cache policy yaru-theme-gnome-shell yaru-theme-gtk yaru-theme-gnome-shell: Installed: 18.10.6 Candidate: 18.10.6 Version table: *** 18.10.6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status yaru-theme-gtk: Installed: 18.10.6 Candidate: 18.10.6 Version table: *** 18.10.6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Package changed: snapd (Ubuntu) => yaru-theme (Ubuntu) ** Description changed: I have recently upgraded from 18.04 LTS to 18.10, but the Yaru theme is not enabled by default nor available to choose in GNOME Tweaks, even though apt says it is already installed. I had the communitheme snap installed when I was using 18.04 LTS, but it stopped working after the upgrade. - $lsb_release -rd + $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ apt-cache policy yaru-theme-gnome-shell yaru-theme-gtk yaru-theme-gnome-shell: - Installed: 18.10.6 - Candidate: 18.10.6 - Version table: - *** 18.10.6 500 - 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 18.10.6 + Candidate: 18.10.6 + Version table: + *** 18.10.6 500 + 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages + 100 /var/lib/dpkg/status yaru-theme-gtk: - Installed: 18.10.6 - Candidate: 18.10.6 - Version table: - *** 18.10.6 500 - 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 18.10.6 + Candidate: 18.10.6 + Version table: + *** 18.10.6 500 + 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1798984 Title: Yaru theme installed but not enabled by default nor available after upgrade to Cosmic Status in yaru-theme package in Ubuntu: New Bug description: I have recently upgraded from 18.04 LTS to 18.10, but the Yaru theme is not enabled by default nor available to choose in GNOME Tweaks, even though apt says it is already installed. I had the communitheme snap installed when I was using 18.04 LTS, but it stopped working after the upgrade. $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ apt-cache policy yaru-theme-gnome-shell yaru-theme-gtk yaru-theme-gnome-shell: Installed: 18.10.6 Candidate: 18.10.6 Version table: *** 18.10.6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status yaru-theme-gtk: Installed: 18.10.6 Candidate: 18.10.6 Version table: *** 18.10.6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1798984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798984] [NEW] Yaru theme installed but not enabled by default nor available after upgrade to Cosmic
You have been subscribed to a public bug: I have recently upgraded from 18.04 LTS to 18.10, but the Yaru theme is not enabled by default nor available to choose in GNOME Tweaks, even though apt says it is already installed. I had the communitheme snap installed when I was using 18.04 LTS, but it stopped working after the upgrade. $lsb_release -rd Description:Ubuntu 18.10 Release:18.10 $ apt-cache policy yaru-theme-gnome-shell yaru-theme-gtk yaru-theme-gnome-shell: Installed: 18.10.6 Candidate: 18.10.6 Version table: *** 18.10.6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status yaru-theme-gtk: Installed: 18.10.6 Candidate: 18.10.6 Version table: *** 18.10.6 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- Yaru theme installed but not enabled by default nor available after upgrade to Cosmic https://bugs.launchpad.net/bugs/1798984 You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme 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 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
I cannot confirm this on my machine. I do not know if what I see it intended behavior, but what I see is still not what either the Gnome 2.28 release notes or the Ubuntu help say should happen. When I enable the OSK in universal access, the OSK opens way too often but not always when it should. This is same in X or Wayland: - Opens when typing on keyboard into Activities or Applications search box. (I don't know if this is good behavior for universal access, but it is not good behavior for general touch use: When I type on the keyboard I don't need an OSK. ) - Opens when I touch into Activities or Applications search box. (OK) - Opens when I start a gnome-term even before I touch it or type into it. But it does not open when I switch focus and touch into an already-open gnome-term. (Not OK) - Does not open with Firefox or Chrome. (May be technically unavoidable, but then requires a way to open the OSK on demand) - In Wayland, swiping up of from the bottom of the screen opens OSK. This does not work in X and I don't see another way) Turning OSK off in Universal access, the behavior becomes better for general touch use as the OSK does not uselessly appear when typing, only when touching - at least in those cases when it does. Otherwise the behavior is unchanged compared to being on in Universal Access. -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798980] [NEW] package libreoffice-common (not installed) failed to install/upgrade: tentative de remplacement de « /usr/bin/soffice », qui appartient aussi au paquet openoffic
Public bug reported: sudo apt install libreoffice-common [sudo] Mot de passe de rafa : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les paquets supplémentaires suivants seront installés : fonts-liberation2 fonts-opensymbol libboost-date-time1.65.1 libboost-filesystem1.65.1 libboost-iostreams1.65.1 libboost-locale1.65.1 libclucene-contribs1v5 libclucene-core1v5 libcmis-0.5-5v5 libeot0 libexttextcat-2.0-0 libexttextcat-data libgpgmepp6 libmythes-1.2-0 liborcus-0.13-0 libpaper-utils libreoffice-core libreoffice-style-galaxy libreoffice-style-tango libxmlsec1 libxmlsec1-nss python3-uno Paquets suggérés : tango-icon-theme Les NOUVEAUX paquets suivants seront installés : fonts-liberation2 fonts-opensymbol libboost-date-time1.65.1 libboost-filesystem1.65.1 libboost-iostreams1.65.1 libboost-locale1.65.1 libclucene-contribs1v5 libclucene-core1v5 libcmis-0.5-5v5 libeot0 libexttextcat-2.0-0 libexttextcat-data libgpgmepp6 libmythes-1.2-0 liborcus-0.13-0 libpaper-utils libreoffice-common libreoffice-core libreoffice-style-galaxy libreoffice-style-tango libxmlsec1 libxmlsec1-nss python3-uno 0 mis à jour, 23 nouvellement installés, 0 à enlever et 4 non mis à jour. Il est nécessaire de prendre 64,8 Mo dans les archives. Après cette opération, 226 Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] o Réception de:1 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 fonts-liberation2 all 2.00.1-7~18.04.1 [1 453 kB] Réception de:2 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 fonts-opensymbol all 2:102.10+LibO6.0.6-0ubuntu0.18.04.1 [92,0 kB] Réception de:3 http://archive.ubuntu.com/ubuntu bionic/main i386 libboost-date-time1.65.1 i386 1.65.1+dfsg-0ubuntu5 [20,7 kB] Réception de:4 http://archive.ubuntu.com/ubuntu bionic/main i386 libboost-filesystem1.65.1 i386 1.65.1+dfsg-0ubuntu5 [44,4 kB] Réception de:5 http://archive.ubuntu.com/ubuntu bionic/main i386 libboost-iostreams1.65.1 i386 1.65.1+dfsg-0ubuntu5 [31,1 kB] Réception de:6 http://archive.ubuntu.com/ubuntu bionic/main i386 libboost-locale1.65.1 i386 1.65.1+dfsg-0ubuntu5 [262 kB] Réception de:7 http://archive.ubuntu.com/ubuntu bionic/main i386 libclucene-core1v5 i386 2.3.3.4+dfsg-1 [507 kB] Réception de:8 http://archive.ubuntu.com/ubuntu bionic/main i386 libclucene-contribs1v5 i386 2.3.3.4+dfsg-1 [81,9 kB] Réception de:9 http://archive.ubuntu.com/ubuntu bionic/main i386 libcmis-0.5-5v5 i386 0.5.1+git20160603-3build2 [511 kB] Réception de:10 http://archive.ubuntu.com/ubuntu bionic/main i386 libeot0 i386 0.01-5 [28,2 kB] Réception de:11 http://archive.ubuntu.com/ubuntu bionic/main i386 libexttextcat-data all 3.4.5-1 [162 kB] Réception de:12 http://archive.ubuntu.com/ubuntu bionic/main i386 libexttextcat-2.0-0 i386 3.4.5-1 [13,9 kB] Réception de:13 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libgpgmepp6 i386 1.10.0-1ubuntu2 [104 kB] Réception de:14 http://archive.ubuntu.com/ubuntu bionic/main i386 libmythes-1.2-0 i386 2:1.2.4-3 [8 594 B] Réception de:15 http://archive.ubuntu.com/ubuntu bionic/main i386 liborcus-0.13-0 i386 0.13.4-2 [396 kB] Réception de:16 http://archive.ubuntu.com/ubuntu bionic/main i386 libpaper-utils i386 1.1.24+nmu5ubuntu1 [8 248 B] Réception de:17 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libreoffice-style-galaxy all 1:6.0.6-0ubuntu0.18.04.1 [1 539 kB] Réception de:18 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libreoffice-style-tango all 1:6.0.6-0ubuntu0.18.04.1 [1 308 kB] Réception de:19 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libreoffice-common all 1:6.0.6-0ubuntu0.18.04.1 [24,7 MB] Réception de:20 http://archive.ubuntu.com/ubuntu bionic/main i386 libxmlsec1 i386 1.2.25-1build1 [117 kB] Réception de:21 http://archive.ubuntu.com/ubuntu bionic/main i386 libxmlsec1-nss i386 1.2.25-1build1 [57,1 kB] Réception de:22 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libreoffice-core i386 1:6.0.6-0ubuntu0.18.04.1 [33,2 MB] Réception de:23 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 python3-uno i386 1:6.0.6-0ubuntu0.18.04.1 [131 kB] 64,8 Mo réceptionnés en 2min 27s (442 ko/s) Sélection du paquet fonts-liberation2 précédemment désélectionné. (Lecture de la base de données... 155292 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../00-fonts-liberation2_2.00.1-7~18.04.1_all.deb ... Dépaquetage de fonts-liberation2 (2.00.1-7~18.04.1) ... Sélection du paquet fonts-opensymbol précédemment désélectionné. Préparation du dépaquetage de .../01-fonts-opensymbol_2%3a102.10+LibO6.0.6-0ubuntu0.18.04.1_all.deb ... Dépaquetage de fonts-opensymbol (2:102.10+LibO6.0.6-0ubuntu0.18.04.1) ... Sélection du paquet libboost-date-time1.65.1:i386 précédemment désélectionné. Préparation du dépaquetage de
[Desktop-packages] [Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted
Re: comment #14: I never said GParted wasn't working - I said that in my case running GParted was causing Disks (gnome-disk-utility) to show buggy behaviour. >From reading the udisks2 issue, the problem seems to do with the udev change event that's triggered either by running GParted or making partition changes using gnome-disk-utility, so our cases may have the same root cause. Running "udevadm info " before and after the triggering action also shows the loss of partition info for me. Perhaps udev is the next place to look, as per udisks issue 425? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1641308 Title: Partitions display wrong in gnome -disks - ok in gparted Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: The partitions displayed by gnome-disk-utility are wrong. When i use gparted the partitions displayed are correct. The display became wrong after i deleted 1 partition from the disk using gnome-disk-utility. Here is a screenshot of the 2 tools vision of the same disk: http://pasteboard.co/PjWpqeNzi.png Here is the fdisk: hippo@hippo-camp:~$ sudo fdisk -l [sudo] password for hippo: Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1c0966b0 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 63 758587953 758587891 361,7G 7 HPFS/NTFS/exFAT /dev/sdc3 758589438 903041023 144451586 68,9G 5 Extended /dev/sdc5 758589440 903041023 144451584 68,9G 83 Linux hippo@hippo-camp:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 gnome-disk-utility: Installed: 3.18.3.1-1ubuntu1 Candidate: 3.18.3.1-1ubuntu1 Version table: *** 3.18.3.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status gparted: Installed: 0.25.0-1 Candidate: 0.25.0-1 Version table: *** 0.25.0-1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I get *very nervous* when tools that have write access to partitions can't display them properly. Good hunt Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-disk-utility 3.18.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 12 12:16:39 2016 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2016-10-11 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1641308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager
You can fix this issue by removing the line "x-scheme-handler/file=exo- file-manager.desktop" from the following files: /usr/share/xubuntu/applications/defaults.list (provided by Xubuntu) ~/.config/mimeapps.list (user overrides) ~/.local/share/applications/mimeapps.list (deprecated) The entry should not be added anymore according to upstream Xfce [1], and it is the cause for the misbehavior according to the comments in the linked Debian report [2]. [1] https://git.xfce.org/xfce/exo/commit/?id=b74caf97642ae2bf00a7754a5fb193f695b6f3d4 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874003#75 ** Also affects: xubuntu-default-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid ** Changed in: xubuntu-default-settings (Ubuntu) Status: New => Confirmed -- 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/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Confirmed Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1778069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Same problem here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
Yes, it auto opens for the apps I mentioned it works. I think I'm using Wayland. Yes, I enabled the OSK in universal access. -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
Thanks Efthimios. I am still a little unclear about what the intended behavior is. Should it auto open when touching a text field e.g. in Chrome? And are you using X or Wayland and it you enable the OSK in Universal Access? Thanks. FWIW, for me on Cosmic it is still as described in the description at least on Wayland, I did not try X recently -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798972] [NEW] package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1
Public bug reported: Automatically notified me of failure to install during upgrade ProblemType: Package DistroRelease: Ubuntu 18.10 Package: emacs-gtk 1:25.2+1-11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sat Oct 20 15:34:10 2018 ErrorMessage: installed emacs-gtk package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-11 (1044 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: emacs Title: package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1798972 Title: package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1 Status in emacs package in Ubuntu: New Bug description: Automatically notified me of failure to install during upgrade ProblemType: Package DistroRelease: Ubuntu 18.10 Package: emacs-gtk 1:25.2+1-11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sat Oct 20 15:34:10 2018 ErrorMessage: installed emacs-gtk package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-11 (1044 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: emacs Title: package emacs-gtk 1:25.2+1-11 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1798972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790762] Re: Ubuntu Software sign in menu needs UI work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1790762 Title: Ubuntu Software sign in menu needs UI work Status in gnome-software package in Ubuntu: Confirmed Bug description: See the attached screenshot. 1. In my opinion, a menu shouldn't show Sign Out (even if greyed out) at the same time as it shows Sign In. There are a few other usability issues. Let me know if you want separate bugs. 2. I am already logged in to Ubuntu Single Sign-On in GNOME Online Accounts, set up with Ubuntu Welcome. 3. The same credentials work for both the Snap Store and Ubuntu One so I think there shouldn't be separate sign in buttons. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.29.92-0ubuntu2 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 4 22:26:58 2018 InstallationDate: Installed on 2017-10-13 (327 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.29.92-0ubuntu2 SourcePackage: gnome-software UpgradeStatus: Upgraded to cosmic on 2018-08-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1790762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
After updating to 18.10, it seems the OSK works as intended in several apps like Chrome, Chromium, the cmd and gedit. Strangely, it doesn't automatically appear in the search box of file explorer. -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted
I've tested with 18.04 and the newer udisks also shows the same behaviour. >From further digging I've found that there is an open issue for a udisks partition property loss bug which seems to be an exact match at https://github.com/storaged-project/udisks/issues/425 ** Bug watch added: github.com/storaged-project/udisks/issues #425 https://github.com/storaged-project/udisks/issues/425 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1641308 Title: Partitions display wrong in gnome -disks - ok in gparted Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: The partitions displayed by gnome-disk-utility are wrong. When i use gparted the partitions displayed are correct. The display became wrong after i deleted 1 partition from the disk using gnome-disk-utility. Here is a screenshot of the 2 tools vision of the same disk: http://pasteboard.co/PjWpqeNzi.png Here is the fdisk: hippo@hippo-camp:~$ sudo fdisk -l [sudo] password for hippo: Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1c0966b0 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 63 758587953 758587891 361,7G 7 HPFS/NTFS/exFAT /dev/sdc3 758589438 903041023 144451586 68,9G 5 Extended /dev/sdc5 758589440 903041023 144451584 68,9G 83 Linux hippo@hippo-camp:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 gnome-disk-utility: Installed: 3.18.3.1-1ubuntu1 Candidate: 3.18.3.1-1ubuntu1 Version table: *** 3.18.3.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status gparted: Installed: 0.25.0-1 Candidate: 0.25.0-1 Version table: *** 0.25.0-1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I get *very nervous* when tools that have write access to partitions can't display them properly. Good hunt Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-disk-utility 3.18.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 12 12:16:39 2016 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2016-10-11 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1641308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798967] [NEW] bubblewrap has wrong description after setuid bit was removed
Public bug reported: After setuid bit was removed from default installation in cosmic (and soon in bionic) the description doesn't match actual behavior anymore: "setuid wrapper for unprivileged chroot and namespace manipulation" ** Affects: bubblewrap (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/1798967 Title: bubblewrap has wrong description after setuid bit was removed Status in bubblewrap package in Ubuntu: Confirmed Bug description: After setuid bit was removed from default installation in cosmic (and soon in bionic) the description doesn't match actual behavior anymore: "setuid wrapper for unprivileged chroot and namespace manipulation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1798967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798967] Re: bubblewrap has wrong description after setuid bit was removed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bubblewrap (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/1798967 Title: bubblewrap has wrong description after setuid bit was removed Status in bubblewrap package in Ubuntu: Confirmed Bug description: After setuid bit was removed from default installation in cosmic (and soon in bionic) the description doesn't match actual behavior anymore: "setuid wrapper for unprivileged chroot and namespace manipulation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1798967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted
OP here, unfortunately I changed my PC since reporting this bug and further testing would be irrevelant. Not sure what you mention is similar though. My issue was with the gnome disk utility, gparted worked perfectly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1641308 Title: Partitions display wrong in gnome -disks - ok in gparted Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: The partitions displayed by gnome-disk-utility are wrong. When i use gparted the partitions displayed are correct. The display became wrong after i deleted 1 partition from the disk using gnome-disk-utility. Here is a screenshot of the 2 tools vision of the same disk: http://pasteboard.co/PjWpqeNzi.png Here is the fdisk: hippo@hippo-camp:~$ sudo fdisk -l [sudo] password for hippo: Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1c0966b0 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 63 758587953 758587891 361,7G 7 HPFS/NTFS/exFAT /dev/sdc3 758589438 903041023 144451586 68,9G 5 Extended /dev/sdc5 758589440 903041023 144451584 68,9G 83 Linux hippo@hippo-camp:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 gnome-disk-utility: Installed: 3.18.3.1-1ubuntu1 Candidate: 3.18.3.1-1ubuntu1 Version table: *** 3.18.3.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status gparted: Installed: 0.25.0-1 Candidate: 0.25.0-1 Version table: *** 0.25.0-1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I get *very nervous* when tools that have write access to partitions can't display them properly. Good hunt Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-disk-utility 3.18.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 12 12:16:39 2016 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2016-10-11 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1641308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted
I see a similar problem with incorrect partition information in gnome- disk-utility. I am not sure if it's exactly the same as the OP's issue as in my case the problem is solely triggered by running GParted, and not by the deletion/modification of partitions as mentioned by the OP. I suspect that GParted is somehow causing udisks2 to report incorrect information. Running "udisksctl info -b /dev/" for the extended partition (the one that's incorrectly displayed by gnome-disk- utility) - shows the Block object's Size is 0 instead of 1024 and "IsContainer" value is false instead of true. Rebooting restores the values to be correct. If the OP is still around and can confirm that udisksctl also shows incorrect partition data in their case, then perhaps this bug would be better assigned to the udisks2 package rather than gnome-disk-utility (there is an upstream bug tracker in Gitlab for the latter in any case). My testing so far has only been on 16.04; there is a newer udisks2 packaged with 18.04 onwards, so if time permits I'll try and replicate this there too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1641308 Title: Partitions display wrong in gnome -disks - ok in gparted Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: The partitions displayed by gnome-disk-utility are wrong. When i use gparted the partitions displayed are correct. The display became wrong after i deleted 1 partition from the disk using gnome-disk-utility. Here is a screenshot of the 2 tools vision of the same disk: http://pasteboard.co/PjWpqeNzi.png Here is the fdisk: hippo@hippo-camp:~$ sudo fdisk -l [sudo] password for hippo: Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1c0966b0 Device Boot Start End Sectors Size Id Type /dev/sdc1 * 63 758587953 758587891 361,7G 7 HPFS/NTFS/exFAT /dev/sdc3 758589438 903041023 144451586 68,9G 5 Extended /dev/sdc5 758589440 903041023 144451584 68,9G 83 Linux hippo@hippo-camp:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 gnome-disk-utility: Installed: 3.18.3.1-1ubuntu1 Candidate: 3.18.3.1-1ubuntu1 Version table: *** 3.18.3.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status gparted: Installed: 0.25.0-1 Candidate: 0.25.0-1 Version table: *** 0.25.0-1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I get *very nervous* when tools that have write access to partitions can't display them properly. Good hunt Matt ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-disk-utility 3.18.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 12 12:16:39 2016 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2016-10-11 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1641308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798943] Re: keyboard backlighting not working on function keys
** Description changed: The keyboard backlighting is not working on function keys. Pressing one of the function key responsible with the backlighting I'm getting this error in Logs: gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed - Also, the keyboard backlighting was working in Ubuntu 18.04 but it doesn't since I upgrade to Ubuntu 18.10. + The keyboard brightness option from the settings doesn't appear anymore. + Also, the keyboard backlighting was working in Ubuntu 18.04 but it doesn't since I upgrade to Ubuntu 18.10. It can be turned off manually with the command: echo 0 | sudo tee /sys/class/leds/smc\:\:kbd_backlight/brightness + ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.30.1.2-1ubuntu2 Uname: Linux 4.18.15-041815-generic Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: 20th of October SourcePackage: gnome-settings-daemon -- 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/1798943 Title: keyboard backlighting not working on function keys Status in gnome-settings-daemon package in Ubuntu: New Bug description: The keyboard backlighting is not working on function keys. Pressing one of the function key responsible with the backlighting I'm getting this error in Logs: gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed The keyboard brightness option from the settings doesn't appear anymore. Also, the keyboard backlighting was working in Ubuntu 18.04 but it doesn't since I upgrade to Ubuntu 18.10. It can be turned off manually with the command: echo 0 | sudo tee /sys/class/leds/smc\:\:kbd_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.30.1.2-1ubuntu2 Uname: Linux 4.18.15-041815-generic Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: 20th of October SourcePackage: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798957] Re: Folders on Desktop are not openned
I've found remains of mate, removed it: $ sudo apt remove -y ubuntu-mate-desktop mate-* ubuntu-mate-* \ plymouth-theme-ubuntu-mate-* lightdm $ sudo apt autoremove -y $ sudo apt install --reinstall -y gdm3 $ sudo reboot Now everything works just fine. Please, close this bug. -- 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/1798957 Title: Folders on Desktop are not openned Status in nautilus package in Ubuntu: New Bug description: Double clicking on any folder located on the Desktop or even right click and then Open, does nothing. System and package info: Description: Ubuntu 18.04.1 LTS Release: 18.04 nautilus: Installed: 1:3.26.4-0~ubuntu18.04.1 Candidate: 1:3.26.4-0~ubuntu18.04.1 Version table: *** 1:3.26.4-0~ubuntu18.04.1 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages What you expected to happen: nautilus executes and displays the folder being "double-clicked". What happened instead: Nothing happens. I did some diagnostics, terminating 'nautilus-desktop' and ran it again using terminal, it logs out the following message: '** (nautilus-desktop:17722): WARNING **: 14:50:00.201: Unable to create File Manager freedesktop proxy: Error calling StartServiceByName for org.freedesktop.FileManager1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.freedesktop.FileManager1: No such file or directory ' In addition, running 'nautilus' prior to running 'nautilus-desktop', then running 'nautilus-desktop', fixes the problem, and now I can open folders from desktop. Terminating 'nautilus' only, I can still open folders from desktop, but only for few seconds where 'nautilus' completely terminates. Additional info: $ ll /etc/dbus-1/system.d total 168 drwxr-xr-x 2 root root 4096 Oct 12 13:43 ./ drwxr-xr-x 4 root root 4096 Jul 25 06:04 ../ -rw-r--r-- 1 root root 1144 Feb 2 2018 avahi-dbus.conf -rw-r--r-- 1 root root 1456 Jun 22 12:27 bluetooth.conf -rw-r--r-- 1 root root 752 Mar 7 2018 com.hp.hplip.conf -rw-r--r-- 1 root root 1007 Apr 3 2018 com.redhat.NewPrinterNotification.conf -rw-r--r-- 1 root root 1016 Apr 3 2018 com.redhat.PrinterDriversInstaller.conf -rw-r--r-- 1 root root 733 Nov 4 2013 com.ubuntu.LanguageSelector.conf -rw-r--r-- 1 root root 759 Feb 18 2014 com.ubuntu.ScreenResolution.Mechanism.conf -rw-r--r-- 1 root root 662 May 2 16:58 com.ubuntu.SoftwareProperties.conf -rw-r--r-- 1 root root 726 Nov 4 2015 com.ubuntu.SystemService.conf -rw-r--r-- 1 root root 766 Apr 29 2015 com.ubuntu.USBCreator.conf -rw-r--r-- 1 root root 929 Oct 11 2017 com.ubuntu.WhoopsiePreferences.conf -rw-r--r-- 1 root root 652 Feb 16 2018 dnsmasq.conf -rw-r--r-- 1 root root 3883 Jun 13 15:04 gdm.conf -rw-r--r-- 1 root root 1016 Dec 2 2017 kerneloops.conf -rw-r--r-- 1 root root 2073 Feb 1 2018 net.hadess.SensorProxy.conf -rw-r--r-- 1 root root 465 Mar 26 2018 nm-dispatcher.conf -rw-r--r-- 1 root root 562 Apr 8 2018 nm-pptp-service.conf -rw-r--r-- 1 root root 434 Feb 11 2009 org.debian.apt.conf -rw-r--r-- 1 root root 917 Dec 18 2017 org.freedesktop.Accounts.conf -rw-r--r-- 1 root root 899 Apr 10 2018 org.freedesktop.bolt.conf -rw-r--r-- 1 root root 1569 Jul 23 2017 org.freedesktop.ColorManager.conf -rw-r--r-- 1 root root 1043 Mar 12 2018 org.freedesktop.fwupd.conf -rw-r--r-- 1 root root 711 Jul 20 2017 org.freedesktop.GeoClue2.Agent.conf -rw-r--r-- 1 root root 1231 Jul 20 2017 org.freedesktop.GeoClue2.conf -rw-r--r-- 1 root root 9662 Apr 24 14:06 org.freedesktop.ModemManager1.conf -rw-r--r-- 1 root root 10309 Mar 26 2018 org.freedesktop.NetworkManager.conf -rw-r--r-- 1 root root 1331 Apr 24 17:13 org.freedesktop.PackageKit.conf -rw-r--r-- 1 root root 632 Jul 13 14:42 org.freedesktop.PolicyKit1.conf -rw-r--r-- 1 root root 1075 Feb 16 2018 org.freedesktop.RealtimeKit1.conf -rw-r--r-- 1 root root 1118 Apr 20 2018 org.freedesktop.thermald.conf -rw-r--r-- 1 root root 525 Jul 12 19:01 org.freedesktop.UDisks2.conf -rw-r--r-- 1 root root 1555 Jan 30 2018 org.freedesktop.UPower.conf -rw-r--r-- 1 root root 765 Apr 18 2018 org.mate.SettingsDaemon.DateTimeMechanism.conf -rw-r--r-- 1 root root 545 Jun 6 17:23 org.opensuse.CupsPkHelper.Mechanism.conf -rw-r--r-- 1 root root 1084 May 21 17:41 pulseaudio-system.conf -rw-r--r-- 1 root root 1513 Feb 5 2018 wpa_supplicant.conf ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64
[Desktop-packages] [Bug 1709164] Re: [MIR] bubblewrap
I just wanted to point out that after dropping setuid bit the package description is now wrong. "setuid wrapper for unprivileged chroot and namespace manipulation" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/1709164 Title: [MIR] bubblewrap Status in bubblewrap package in Ubuntu: Fix Released Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = The gnome-desktop3 library 3.25.90+ requires bubblewrap. bubblewrap is most commonly used as part of Flatpak's security isolation feature. Here it's being used to sandbox the thumbnailers. See https://git.gnome.org/browse/gnome-desktop/log (changes from 3.25.4 to 3.25.90) The bubblewrap feature was disabled in Ubuntu 17.10's gnome-desktop3 package because this MIR was not processed. Security No known open security vulnerabilities in any Ubuntu releases. https://security-tracker.debian.org/tracker/source-package/bubblewrap I helped prepare a security update (LP: #1657357) (CVE-2017-5226) for bubblewrap/flatpak several months ago. Security-sensitive package. Quality assurance = Bug subscriber: should be Ubuntu Desktop Bugs https://bugs.launchpad.net/ubuntu/+source/bubblewrap https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=bubblewrap https://github.com/projectatomic/bubblewrap/issues dh_auto_test runs the build tests but they appear to be set as SKIP upstream. (See comment #4) Multiple autopkgtests passing on all Ubuntu architectures. Because the tests require machine isolation, the autopkgtests don't run on Debian's infrastructure currently. Dependencies check-mir reports all other binary dependencies are in main Standards compliance 4.0.0 Maintenance === - Actively developed upstream https://github.com/projectatomic/bubblewrap - Maintained in Debian by the pkg-utopia team but more specifically, it is maintained by Simon McVittie (smcv) who also maintains Flatpak and ostree in Debian and Ubuntu. short dh7 style rules, dh compat 10 Background information == William Hua (attente) had been working last year on a snapcraft plugin that used bubblewrap. So maybe more stuff will use bubblewrap in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1709164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
Removing the timidity package resolved this for me. But the symptoms are strange: Symptoms after upgrading from 18.04 to 18:10: - aplay -l shows all audio devices as expected, including internal on-board sound device - pavucontrol only shows hdmi3 output, analog sound is missing from options Removing timidity (just out of frustration because I couldn't find any other suggestions on this) and rebooting once brought back the analog sound devices Thanks to JR for mentioning this. -- 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/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
Update: Probably related to this report: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1798466 -- 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/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798957] [NEW] Folders on Desktop are not openned
Public bug reported: Double clicking on any folder located on the Desktop or even right click and then Open, does nothing. System and package info: Description:Ubuntu 18.04.1 LTS Release:18.04 nautilus: Installed: 1:3.26.4-0~ubuntu18.04.1 Candidate: 1:3.26.4-0~ubuntu18.04.1 Version table: *** 1:3.26.4-0~ubuntu18.04.1 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages What you expected to happen: nautilus executes and displays the folder being "double-clicked". What happened instead: Nothing happens. I did some diagnostics, terminating 'nautilus-desktop' and ran it again using terminal, it logs out the following message: '** (nautilus-desktop:17722): WARNING **: 14:50:00.201: Unable to create File Manager freedesktop proxy: Error calling StartServiceByName for org.freedesktop.FileManager1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.freedesktop.FileManager1: No such file or directory ' In addition, running 'nautilus' prior to running 'nautilus-desktop', then running 'nautilus-desktop', fixes the problem, and now I can open folders from desktop. Terminating 'nautilus' only, I can still open folders from desktop, but only for few seconds where 'nautilus' completely terminates. Additional info: $ ll /etc/dbus-1/system.d total 168 drwxr-xr-x 2 root root 4096 Oct 12 13:43 ./ drwxr-xr-x 4 root root 4096 Jul 25 06:04 ../ -rw-r--r-- 1 root root 1144 Feb 2 2018 avahi-dbus.conf -rw-r--r-- 1 root root 1456 Jun 22 12:27 bluetooth.conf -rw-r--r-- 1 root root 752 Mar 7 2018 com.hp.hplip.conf -rw-r--r-- 1 root root 1007 Apr 3 2018 com.redhat.NewPrinterNotification.conf -rw-r--r-- 1 root root 1016 Apr 3 2018 com.redhat.PrinterDriversInstaller.conf -rw-r--r-- 1 root root 733 Nov 4 2013 com.ubuntu.LanguageSelector.conf -rw-r--r-- 1 root root 759 Feb 18 2014 com.ubuntu.ScreenResolution.Mechanism.conf -rw-r--r-- 1 root root 662 May 2 16:58 com.ubuntu.SoftwareProperties.conf -rw-r--r-- 1 root root 726 Nov 4 2015 com.ubuntu.SystemService.conf -rw-r--r-- 1 root root 766 Apr 29 2015 com.ubuntu.USBCreator.conf -rw-r--r-- 1 root root 929 Oct 11 2017 com.ubuntu.WhoopsiePreferences.conf -rw-r--r-- 1 root root 652 Feb 16 2018 dnsmasq.conf -rw-r--r-- 1 root root 3883 Jun 13 15:04 gdm.conf -rw-r--r-- 1 root root 1016 Dec 2 2017 kerneloops.conf -rw-r--r-- 1 root root 2073 Feb 1 2018 net.hadess.SensorProxy.conf -rw-r--r-- 1 root root 465 Mar 26 2018 nm-dispatcher.conf -rw-r--r-- 1 root root 562 Apr 8 2018 nm-pptp-service.conf -rw-r--r-- 1 root root 434 Feb 11 2009 org.debian.apt.conf -rw-r--r-- 1 root root 917 Dec 18 2017 org.freedesktop.Accounts.conf -rw-r--r-- 1 root root 899 Apr 10 2018 org.freedesktop.bolt.conf -rw-r--r-- 1 root root 1569 Jul 23 2017 org.freedesktop.ColorManager.conf -rw-r--r-- 1 root root 1043 Mar 12 2018 org.freedesktop.fwupd.conf -rw-r--r-- 1 root root 711 Jul 20 2017 org.freedesktop.GeoClue2.Agent.conf -rw-r--r-- 1 root root 1231 Jul 20 2017 org.freedesktop.GeoClue2.conf -rw-r--r-- 1 root root 9662 Apr 24 14:06 org.freedesktop.ModemManager1.conf -rw-r--r-- 1 root root 10309 Mar 26 2018 org.freedesktop.NetworkManager.conf -rw-r--r-- 1 root root 1331 Apr 24 17:13 org.freedesktop.PackageKit.conf -rw-r--r-- 1 root root 632 Jul 13 14:42 org.freedesktop.PolicyKit1.conf -rw-r--r-- 1 root root 1075 Feb 16 2018 org.freedesktop.RealtimeKit1.conf -rw-r--r-- 1 root root 1118 Apr 20 2018 org.freedesktop.thermald.conf -rw-r--r-- 1 root root 525 Jul 12 19:01 org.freedesktop.UDisks2.conf -rw-r--r-- 1 root root 1555 Jan 30 2018 org.freedesktop.UPower.conf -rw-r--r-- 1 root root 765 Apr 18 2018 org.mate.SettingsDaemon.DateTimeMechanism.conf -rw-r--r-- 1 root root 545 Jun 6 17:23 org.opensuse.CupsPkHelper.Mechanism.conf -rw-r--r-- 1 root root 1084 May 21 17:41 pulseaudio-system.conf -rw-r--r-- 1 root root 1513 Feb 5 2018 wpa_supplicant.conf ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 14:54:36 2018 InstallationDate: Installed on 2018-09-20 (29 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member
[Desktop-packages] [Bug 1798629] Re: [snap] System monitor or calculator don't use the right min, max and close icons
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1798629 Title: [snap] System monitor or calculator don't use the right min, max and close icons Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: Open System Monitor or Calculator app on Ubuntu 18.10. Observe the minimize, maximize, close icons. These are much bolder and different from non-snap apps. This is more noticeable when the window is maximized. The app icon itself is as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1798629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1509559] Re: Lack sensitivity mouse option
Can someone responsible please reply to this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1509559 Title: Lack sensitivity mouse option Status in unity-control-center package in Ubuntu: Confirmed Bug description: Ubuntu 15.10 Unity x64 unity-control-center mouse There aren't options for mouse sensitivity. The sensitivity of my mouse gamer (Multilaser M3T4L W4R M0207) is high, There aren't options for mouse sensitivity, I'm running a script to correct speed: #!/bin/bash xinput --set-prop "11" "Device Accel Constant Deceleration" 1.5 Please check this... Thank you!!! See more detail: Ubuntu 15.10 Unity x64 ~$ xinput --list --short ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Game Keyboard id=9 [slave pointer (2)] ⎜ ↳ LXD Gaming Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ Game Keyboard id=8 [slave keyboard (3)] ↳ LXD Gaming Mouse id=10 [slave keyboard (3)] ~$ xinput --list-props "11" Device 'LXD Gaming Mouse': Device Enabled (151): 1 Coordinate Transformation Matrix (153): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (277): 0 Device Accel Constant Deceleration (278): 1.00 Device Accel Adaptive Deceleration (279): 1.00 Device Accel Velocity Scaling (280): 10.00 Device Product ID (271): 7511, 44292 Device Node (272): "/dev/input/event13" Evdev Axis Inversion (281): 0, 0 Evdev Axes Swap (283): 0 Axis Labels (284): "Rel X" (161), "Rel Y" (162), "Rel Horiz Wheel" (276), "Rel Vert Wheel" (301) Button Labels (285): "Button Left" (154), "Button Middle" (155), "Button Right" (156), "Button Wheel Up" (157), "Button Wheel Down" (158), "Button Horiz Wheel Left" (159), "Button Horiz Wheel Right" (160), "Button Side" (299), "Button Extra" (300), "Button Unknown" (274), "Button Unknown" (274), "Button Unknown" (274), "Button Unknown" (274) Evdev Scrolling Distance (286): 1, 1, 1 Evdev Middle Button Emulation (287): 0 Evdev Middle Button Timeout (288): 50 Evdev Third Button Emulation (289): 0 Evdev Third Button Emulation Timeout (290): 1000 Evdev Third Button Emulation Button (291): 3 Evdev Third Button Emulation Threshold (292): 20 Evdev Wheel Emulation (293): 0 Evdev Wheel Emulation Axes (294): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (295): 10 Evdev Wheel Emulation Timeout (296): 200 Evdev Wheel Emulation Button (297): 4 Evdev Drag Lock Buttons (298): 0 ~$ lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H67 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1) 03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01) 05:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1509559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1798941] Re: back button does nothing
*** This bug is a duplicate of bug 1798053 *** https://bugs.launchpad.net/bugs/1798053 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1798053, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1798053 Click on the back icon in gnome-software don't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798941 Title: back button does nothing Status in gnome-software package in Ubuntu: New Bug description: Steps: 1. Open Ubuntu Software 2. Search for "Dropbox" 3. Install it 4. Launch it 5. Click back button < in the top left corner. Expecting it navigates back to search or main view, but nothing happens. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 11:00:16 2018 InstallationDate: Installed on 2018-10-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu7 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798952] Re: Ubuntu Software back button does not work
*** This bug is a duplicate of bug 1798053 *** https://bugs.launchpad.net/bugs/1798053 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1798053, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1798053 Click on the back icon in gnome-software don't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798952 Title: Ubuntu Software back button does not work Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Software back button generally does not operate. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 14:01:51 2018 InstallationDate: Installed on 2018-10-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu5 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1024742] Re: Mouse sensitivity is actually acceleration threshold. No way to change sensitivity.
Sad to see this unanswered until now, where it is not relevant anymore, since the whole control center has changed alot. But still this bug is open... I guess Ubuntu is heavily lacking staff not only to keep track of relevant bug reports but even to keep this bug tracker organized. -- 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/1024742 Title: Mouse sensitivity is actually acceleration threshold. No way to change sensitivity. Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In the mouse settings there are two sliders: acceleration and sensitivity. Acceleration works (roughly) as expected, although it is kind of too binary (either you're going at a slow speed or a high speed; nothing in-between). However the sensitivity at first seems to do absolutely nothing (if you have no acceleration at least). After playing around with it, and reading some forums I found that the "sensitivity" is actually mislabelled, and it is really the acceleration threshold! There is also no actual sensitivity setting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sat Jul 14 17:16:14 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1024742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
Can someone responsible for this (is there anyone?) please update this to reflect the current state? -- 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/124440 Title: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed Status in gnome-control-center: Unknown Status in GTK+: Unknown Status in Mir: Fix Released Status in Unity: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Triaged Bug description: This has been driving me nuts for a while now. The scroll wheel on my desktop mouse (it's an MS wireless optical mouse model 1008) scrolls rather fast. Instead of moving a few lines, it scrolls half a page or more with a very gentle scroll. The bluetooth mouse I use with my laptop does not do this so it's probably somewhat hardware specific. However, I'm wondering if there is a way to modify the speed or sensitivity. I found an answer here from about a year ago (https://answers.launchpad.net/ubuntu/+question/1339) that suggests there isn't a way but I'm wondering if anything has changed since then. I've also skimmed through synaptic but didn't see anything promising (like gsynaptic for touchpads). Thanks. See https://answers.launchpad.net/ubuntu/+question/9200 for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798712] Re: No sound (18.10 Cosmic)
It looks like it successfully starts after a long delay (more than 1 hour, no clue how long). -- 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/1798712 Title: No sound (18.10 Cosmic) Status in pulseaudio package in Ubuntu: New Bug description: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798952] [NEW] Ubuntu Software back button does not work
Public bug reported: Ubuntu Software back button generally does not operate. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 14:01:51 2018 InstallationDate: Installed on 2018-10-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu5 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798952 Title: Ubuntu Software back button does not work Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Software back button generally does not operate. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 14:01:51 2018 InstallationDate: Installed on 2018-10-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu5 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798799] Re: lightning add on not compatible with latest release
@Ryan It is still installed - it was working fine before latest update
to Thunderbird
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1798799
Title:
lightning add on not compatible with latest release
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Lightning 5.4 is disabled as it is not compatible with Thunderbird 60.2.1
I get this on two separate machines.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:60.2.1+build1-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tom1853 F pulseaudio
BuildID: 20181010142617
Channel: Unavailable
CurrentDesktop: XFCE
Date: Fri Oct 19 11:32:43 2018
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
IpRoute:
default via 192.168.2.254 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.64 metric 600
MostRecentCrashID: bp-80fbbbfc-d94c-4bb6-a8dc-cc6580180917
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181010142617 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to bionic on 2018-09-08 (41 days ago)
dmi.bios.date: 11/25/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.03
dmi.board.asset.tag: Tag 12345
dmi.board.name: W65_W67RZ
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd11/25/2015:svnPCSpecialistLimited:pnW65_W67RZ:pvrNotApplicable:rvnCLEVO:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W65_W67RZ
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist Limited
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798799/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798950] [NEW] Cannot boot to a graphical desktop, black screen before login prompt.
Public bug reported: Upgraded from 18.04 to 18.10, did not boot afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sat Oct 20 11:38:43 2018 InstallationDate: Installed on 2018-09-20 (29 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- 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/1798950 Title: Cannot boot to a graphical desktop, black screen before login prompt. Status in lightdm package in Ubuntu: New Bug description: Upgraded from 18.04 to 18.10, did not boot afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Sat Oct 20 11:38:43 2018 InstallationDate: Installed on 2018-09-20 (29 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1798950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Yes this is exactly the problem I have. Every-time I install the Nvidia- drivers the machine won't boot up it hangs and displays "Failed to connect to lvmetad. Falling back to device scanning. /dev/mapper/ubuntu--vg--root" I even tried installing earlier drivers -340 or 361 . The problem persists. The only time it boots up is when I purge the Nvidia drivers. This started soon after I upgraded to 18.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769736] Re: [snap] Custom app menu entries do not work
It makes no sense to fix this bug or LP: #1797888 due to https://gitlab.gnome.org/GNOME/Initiatives/wikis/App-Menu-Retirement. May I tempt you to https://bugs.documentfoundation.org/show_bug.cgi?id=119996 ? ** Bug watch added: Document Foundation Bugzilla #119996 https://bugs.documentfoundation.org/show_bug.cgi?id=119996 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1769736 Title: [snap] Custom app menu entries do not work Status in libreoffice package in Ubuntu: Triaged Bug description: When launching e.g. libreoffice.writer, the application exposes a custom menu in the top panel with entries to create a new document, open the preferences, display the help and about dialog, and exit the application. See attached screenshot. None of these entries have any effect (not even the "Quit" one). $ snap info libreoffice snap-id: CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v tracking: candidate refreshed: 2018-05-02T15:58:07+02:00 installed: 6.0.4.1 (61) 479MB - channels: stable:6.0.3.2 (59) 479MB - candidate: 6.0.4.1 (61) 479MB - beta: ↑ edge: ↑ $ snap info core type: core snap-id: 99T7MUlRhtI3U0QFgl5mXXESAiSwt776 tracking: stable refreshed: 2018-04-29T20:29:48+02:00 installed: 16-2.32.6(4571) 90MB core channels: stable:16-2.32.6(4571) 90MB - candidate: 16-2.32.6(4571) 90MB - beta: 16-2.32.6(4571) 90MB - edge: 16-2.32.6+git710.8eefd85 (4619) 91MB - $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1769736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798541] Re: Please update to actual 3.18.9 version
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1798541 Title: Please update to actual 3.18.9 version Status in hplip package in Ubuntu: New Bug description: Please update to actual 3.18.9 version: a lot of new printers were added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1798541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798943] [NEW] keyboard backlighting not working on function keys
Public bug reported: The keyboard backlighting is not working on function keys. Pressing one of the function key responsible with the backlighting I'm getting this error in Logs: gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Also, the keyboard backlighting was working in Ubuntu 18.04 but it doesn't since I upgrade to Ubuntu 18.10. It can be turned off manually with the command: echo 0 | sudo tee /sys/class/leds/smc\:\:kbd_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.30.1.2-1ubuntu2 Uname: Linux 4.18.15-041815-generic Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: 20th of October SourcePackage: gnome-settings-daemon ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/1798943 Title: keyboard backlighting not working on function keys Status in gnome-settings-daemon package in Ubuntu: New Bug description: The keyboard backlighting is not working on function keys. Pressing one of the function key responsible with the backlighting I'm getting this error in Logs: gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Also, the keyboard backlighting was working in Ubuntu 18.04 but it doesn't since I upgrade to Ubuntu 18.10. It can be turned off manually with the command: echo 0 | sudo tee /sys/class/leds/smc\:\:kbd_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.30.1.2-1ubuntu2 Uname: Linux 4.18.15-041815-generic Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: 20th of October SourcePackage: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798103] Re: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2
** Changed in: firefox (Ubuntu) Importance: Undecided => Low -- 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/1798103 Title: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2 Status in firefox package in Ubuntu: New Bug description: == The issue == Search and text selection highlighting visuals get mismatched with the actual selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 or larger. == Steps to reproduce == * Open `about:config`, find `layout.css.devPixelsPerPx` and change the value from default (-1.0) to 1.2. * Open a view-source view with long lines: `view-source:https://www.youtube.com/user/10asti10` * hit Ctrl+f, search for rss * using the LMB, try selecting some text, then copy and paste it somewhere == What happens == Screenshot 1: the highlighted text on the page is not ”rss”. The highlight doesn’t even adhere to letter widths. Screenshot 2: the pasted text is not even close to what you’ve selected to copy. == What I expect to happen == For the search to hightlight an occurence of ”rss”, and for the pasted text to correspond to what I’ve selected from the view-source view. == Other info == * In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, whereas 1.2 and anything above does. * In addition to 18.04 (whence the attached info is from) I’ve reproduced this in a VM running up-to-date 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 62.0.3+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BuildID: 20181002130007 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 16:59:28 2018 InstallationDate: Installed on 2016-10-13 (733 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731454] Re: Video doesn’t play in the right screen on entering full-screen mode while using two monitors
** Summary changed: - O video não é reproduzido na tela certa quando entra em modo tela cheia quando se utiliza 2 monitores + Video doesn’t play in the right screen on entering full-screen mode while using two monitors -- 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/1731454 Title: Video doesn’t play in the right screen on entering full-screen mode while using two monitors Status in firefox package in Ubuntu: New Bug description: O quando estou com 2 monitores o e ativo o modo Tela Cheia do video o video sai do monitor de origem e vai para o outro monitor secundario. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krashtime 1715 F pulseaudio BuildID: 20171003101344 Channel: Unavailable CurrentDesktop: GNOME Date: Fri Nov 10 08:15:13 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-11-10 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.15.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.15.0/24 dev wlp2s0 proto kernel scope link src 192.168.15.41 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: prefs.js ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003101344 (In use) RelatedPackageVersions: adobe-flashplugin 1:20171025.1-0ubuntu0.16.04.1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd03/17/2017:svnAcer:pnAspireVX5-591G:pvrV1.05:rvnKBL:rnWish_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.name: Aspire VX5-591G dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1731454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798941] [NEW] back button does nothing
Public bug reported: Steps: 1. Open Ubuntu Software 2. Search for "Dropbox" 3. Install it 4. Launch it 5. Click back button < in the top left corner. Expecting it navigates back to search or main view, but nothing happens. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 11:00:16 2018 InstallationDate: Installed on 2018-10-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu7 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798941 Title: back button does nothing Status in gnome-software package in Ubuntu: New Bug description: Steps: 1. Open Ubuntu Software 2. Search for "Dropbox" 3. Install it 4. Launch it 5. Click back button < in the top left corner. Expecting it navigates back to search or main view, but nothing happens. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 11:00:16 2018 InstallationDate: Installed on 2018-10-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu7 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798939] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1798939 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Just tried to install NVIDIA drivers ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 20 09:31:09 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-h4ndlf/3-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-28 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1798939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798939] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-com
Public bug reported: Just tried to install NVIDIA drivers ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 20 09:31:09 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-h4ndlf/3-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-28 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1798939 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Just tried to install NVIDIA drivers ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 20 09:31:09 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-h4ndlf/3-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-28 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1798939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
