[Desktop-packages] [Bug 1686606] [NEW] hello.I use ubuntu mate 16.04 lts.I have one bug to report about suspend in acer aspire 7720g with ge force 8400M GS card .I set up on 340.102 proprietary tested
Public bug reported: I use acer aspire 7720G with nvidia geforce 8400M gs card 256 mb ,and have problem with a suspend on ubuntu 16.04 mate lts .when I restart computer then it works fine ,but when I normally shutdown and turn it on again ,and put into suspend ,it wont resume from suspend ,so I need to restart and suspend then works good.when suspend doesnt work black screen on laptop is shown up ,keyboard,touchpad doesnt work at all ,then I must put on a force shutdown ,and then restart that suspend can work again.please help,I use nvidia driver version 340.102 tested everything else works fine ,only suspend not.system is fully updated ,newest kernel in use.thanks,bye ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- 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/1686606 Title: hello.I use ubuntu mate 16.04 lts.I have one bug to report about suspend in acer aspire 7720g with ge force 8400M GS card .I set up on 340.102 proprietary tested driver ,but there is that bug on a suspend ,when I shut down the computer ,and start over to work I,when I put into suspend I cant wake my laptop,my screen is black,laptop turns on but the screen is black,keyboard,touchpad ,nothing reacts at all,so I need to restart laptop and then suspend works fine.let me resume,when I push shutdown and turn laptop again suspend doesnt work at all so I need to restart laptop to meke it work again.please help.acer aspire 7720G ,nvidia ge force 8400M gs card ,intel core 2 duo 7250 2.o ghz ,2gb ddr2 ram,.thanks, Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I use acer aspire 7720G with nvidia geforce 8400M gs card 256 mb ,and have problem with a suspend on ubuntu 16.04 mate lts .when I restart computer then it works fine ,but when I normally shutdown and turn it on again ,and put into suspend ,it wont resume from suspend ,so I need to restart and suspend then works good.when suspend doesnt work black screen on laptop is shown up ,keyboard,touchpad doesnt work at all ,then I must put on a force shutdown ,and then restart that suspend can work again.please help,I use nvidia driver version 340.102 tested everything else works fine ,only suspend not.system is fully updated ,newest kernel in use.thanks,bye To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1686606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1669100] Re: Please disable gconf in chromium-browser
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1669100 Title: Please disable gconf in chromium-browser Status in chromium-browser package in Ubuntu: In Progress Bug description: gconf has been deprecated for years and I'd like to remove it from my computer. (It's not used by Unity or unity-settings-daemon or core GNOME at all.) Ubuntu's debian/rules has use_gconf=true but Debian has use_gconf=false. Please follow Debian here. I see that the apport script also tries to use gconf so that should be dropped too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1669100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
There's a new 7260 firmware, can you try it? 1. Download https://git.kernel.org/pub/scm/linux/kernel/git/firmware /linux-firmware.git/plain/iwlwifi-7260-17.ucode 2. Put 'iwlwifi-7260-17.ucode' to /lib/firmware 3. Reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683997] Re: Firefox scrollbars are too narrow and difficult to use in Zesty
As an aside, oddly enough, it doesn't affect everything. Nautilus is ignoring the theme settings and still has an horizontally-expanding sidebar on hover with my workaround in place. But that's probably a bug in Nautilus. -- 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/1683997 Title: Firefox scrollbars are too narrow and difficult to use in Zesty Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 52.0.1 in Ubuntu 17.04 has very narrow scrollbars that are difficult to click on using a mouse - they are about one-third of the width of the 'old-style' scrollbars used throughout most of Ubuntu until a few weeks ago. (ubuntu-gnome has the same problem, fwiw.) The expected behaviour is that the scrollbars should widen when you hover over them, the same as with other gnome 3.20+ apps. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 52.0.1+build2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1598 F pulseaudio BuildID: 20170321232041 Channel: Unavailable Date: Wed Apr 19 11:51:57 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-04-13 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) IpRoute: default via 10.0.2.2 dev enp0s3 proto static metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 IwConfig: lono wireless extensions. enp0s3no wireless extensions. Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=52.0.1/20170321232041 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1683997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 481281] Re: thunderbird cannot use socks proxy
also affects thunderbird 45.8.0 in zesty -- 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/481281 Title: thunderbird cannot use socks proxy Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird Thunderbird seems not to be able to use SOCK proxies even though they are listed as an option. In some cases this means denial of access. In other cases it means choosing between and insecure network connection and denial of access. Firefox can use SOCKS5 proxies and Thunderbird has a very similar preferences dialog. When configured with the same proxy settings that work just fine for Firefox, Thunderbird gives and error message: "Failed to connect to server " The proxy settings can be found: Edit->Preferences->Advanced->Network&Disk Space->Connection->Manual Proxy Configuration->SOCKS ... $ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 $ apt-cache policy thunderbird thunderbird: Installed: 2.0.0.23+build1+nobinonly-0ubuntu1 Candidate: 2.0.0.23+build1+nobinonly-0ubuntu1 Version table: *** 2.0.0.23+build1+nobinonly-0ubuntu1 0 500 http://fi.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/481281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686456] Re: Font size in tab titles too big compared to Windows since material design
Thanks for the detailed report! Chromium actually uses the default font and font size configured on the system. You can change that in gnome-tweak-tool, go to "Fonts > Interface" and select a different font/size. I’ll mark this bug invalid as this is behaving as designed. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1686456 Title: Font size in tab titles too big compared to Windows since material design Status in chromium-browser package in Ubuntu: Invalid Bug description: Since Chromium's material design "update", font size in the tab titles is too large on Ubuntu 14.04 with Unity. It is way larger than it was on Ubuntu before the material design update, and still considerably larger than a current Chrome version on Windows 7, so this should probably be considered a bug. It makes less of the tab title visible compared to current Chrome on Windows 7 (and compared to old Chromium on Ubuntu) and as such less useful. See attachments for a comparison between Chrome 58.0.3029.81 on Windows 7 and Ubuntu's Chromium 58.0.3029.81-0ubuntu0.14.04.1172. On the screenshot in Windows 7, the title text "New Tab" is 47 px wide and 9 px tall. In Ubuntu, the same text is 58 px wide and 12 px tall. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1686456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
Okay, I did a whole bunch of things tonight and I think I got mine working. Added " options snd-hda-intel model=auto " to /etc/modprobe.d/alsa-base.conf (https://forums.linuxmint.com/viewtopic.php?t=110209) Added " sudo apt-get install dkms " and downloading the most recent ALSA daily for 16.04 (https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS) Added " rmmod snd_hda_intel " and " modprobe snd_hda_intel position_fix=1 " to /etc/rc.local (https://github.com/ValveSoftware/SteamOS/issues/221) Executed " sudo apt-get install --install-recommends linux-generic-lts-wily xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video-all-lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts-wily " (https://ubuntuforums.org/showthread.php?t=2293912) Installed hdajackretask [per mephi, #81 in this thread], selected Creative CA0132, and toggled Advanced override. Override Green Headphone, Front side. Set Device to Headphone and Channel (in group) to Front. Also the simple stuff like making sure your desired audio output device is set to default and not muted. Make sure to run alsamixer after each reboot because I find my output muted after every restart. Hope this helps someone! ** Bug watch added: github.com/ValveSoftware/SteamOS/issues #221 https://github.com/ValveSoftware/SteamOS/issues/221 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 702452]
I maintain the taskbar in KDE's Plasma 5. We have the same problem that Gnome Shell and Unity do. Is there any chance we can get wine to set StartupWMClass in the .desktop files it generates to the executable name it sets in WM_CLASS so we can match without unreliable hackery? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/702452 Title: [launcher] Wine applications are wrongly matched Status in BAMF: Confirmed Status in libwnck: Fix Released Status in Unity: Confirmed Status in Wine: Unknown Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: After launching a Wine app from terminal or via gnome-do, it appears in the launcher with the Wine icon, instead of its own icon. The title is "Wine Window Program Loader" instead of the proper application name. It can't be favorited since it will favorite the wine executable itself. And obviously different wine apps are all grouped under the same launcher icon. See also bug #635223 about Wine applications not showing up in the dash. - A way to fix this is to make all the Wine generated .desktop file to include a StartupWMClass value that matches the instance name of the related program (generally the .exe file name to be executed). So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding this parameter: StartupWMClass=firefox.exe Wine should try to add this information at file generation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/702452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 702452]
(In reply to Eike Hein from comment #13) > I've started a thread on wine-devel that goes into greater detail on this > issue: https://www.winehq.org/pipermail/wine-devel/2017-April/117413.html Since you are so aware of the issue are you able to form a better fix? Basically anyone can contribute to wine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/702452 Title: [launcher] Wine applications are wrongly matched Status in BAMF: Confirmed Status in libwnck: Fix Released Status in Unity: Confirmed Status in Wine: Unknown Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: After launching a Wine app from terminal or via gnome-do, it appears in the launcher with the Wine icon, instead of its own icon. The title is "Wine Window Program Loader" instead of the proper application name. It can't be favorited since it will favorite the wine executable itself. And obviously different wine apps are all grouped under the same launcher icon. See also bug #635223 about Wine applications not showing up in the dash. - A way to fix this is to make all the Wine generated .desktop file to include a StartupWMClass value that matches the instance name of the related program (generally the .exe file name to be executed). So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding this parameter: StartupWMClass=firefox.exe Wine should try to add this information at file generation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/702452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 702452]
I've started a thread on wine-devel that goes into greater detail on this issue: https://www.winehq.org/pipermail/wine- devel/2017-April/117413.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/702452 Title: [launcher] Wine applications are wrongly matched Status in BAMF: Confirmed Status in libwnck: Fix Released Status in Unity: Confirmed Status in Wine: Unknown Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: After launching a Wine app from terminal or via gnome-do, it appears in the launcher with the Wine icon, instead of its own icon. The title is "Wine Window Program Loader" instead of the proper application name. It can't be favorited since it will favorite the wine executable itself. And obviously different wine apps are all grouped under the same launcher icon. See also bug #635223 about Wine applications not showing up in the dash. - A way to fix this is to make all the Wine generated .desktop file to include a StartupWMClass value that matches the instance name of the related program (generally the .exe file name to be executed). So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding this parameter: StartupWMClass=firefox.exe Wine should try to add this information at file generation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/702452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 702452]
I'm really really hoping for someone more qualified to pop up (since I don't know the wine codebase), but failing that I can try to take a stab at it yes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/702452 Title: [launcher] Wine applications are wrongly matched Status in BAMF: Confirmed Status in libwnck: Fix Released Status in Unity: Confirmed Status in Wine: Unknown Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: After launching a Wine app from terminal or via gnome-do, it appears in the launcher with the Wine icon, instead of its own icon. The title is "Wine Window Program Loader" instead of the proper application name. It can't be favorited since it will favorite the wine executable itself. And obviously different wine apps are all grouped under the same launcher icon. See also bug #635223 about Wine applications not showing up in the dash. - A way to fix this is to make all the Wine generated .desktop file to include a StartupWMClass value that matches the instance name of the related program (generally the .exe file name to be executed). So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding this parameter: StartupWMClass=firefox.exe Wine should try to add this information at file generation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/702452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 38440] Re: Evolution defaults to saving sent mail and drafts locally when an IMAP account is setup.
** Changed in: evolution Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/38440 Title: Evolution defaults to saving sent mail and drafts locally when an IMAP account is setup. Status in Evolution: Invalid Status in evolution package in Ubuntu: Invalid Bug description: When I setup an IMAP account in Evolution, it defaults to saving any email I send out and any email I save as a draft locally instead of on the IMAP server. It would be nice if it defaulted to save outgoing messages and drafts of an IMAP account on the IMAP server and not locally. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/38440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685112] Re: Fails ACID3 test
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1685112 Title: Fails ACID3 test Status in firefox package in Ubuntu: Confirmed Bug description: It fails the acid3.acidtests.org. The reported failure is: Test 35 failed: expected '0' but got '1' - root element, with no parent node, claims to be a :first-child See attached screenshot. The same failure is happening also to Google Chrome 58.0.3029.81. Previous versions used to succeed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 53.0+build6-0ubuntu0.16.04.1 Uname: Linux 4.10.11-041011-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: enzo 3368 F pulseaudio BuildID: 20170418123315 Channel: Unavailable CurrentDesktop: KDE Date: Fri Apr 21 09:10:58 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) IpRoute: default via 192.168.254.254 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.254.0/24 dev enp2s0 proto kernel scope link src 192.168.254.42 metric 100 IwConfig: lono wireless extensions. enp2s0no wireless extensions. Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=53.0/20170418123315 (In use) RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L02 v02.01 dmi.board.asset.tag: CZC3523T17 dmi.board.name: 18EB dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3523T17 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP ProDesk 490 G1 MT dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1685112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686568] Re: Firefox Does Not Respond. Process can not be killed. Terminal commands to kill the process freeze. Logout Freeze.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1686568 Title: Firefox Does Not Respond. Process can not be killed. Terminal commands to kill the process freeze. Logout Freeze. Status in firefox package in Ubuntu: Confirmed Bug description: Firefox goes unresponsive occasionally after the latest kernel update. Can force-kill the window but the process can not be killed. Reboot stalls. Logout freezes the system. Must hard-reboot by long-pressing the power button to get back to normal and the same repeats randomly. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 53.0+build6-0ubuntu0.17.04.1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: murat 2753 F pulseaudio /dev/snd/controlC0: murat 2753 F pulseaudio BuildID: 20170418122848 Channel: Unavailable Date: Wed Apr 26 20:54:33 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 2016-01-26 (456 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto static metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.8 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=52.0.1/20170317212642 (Out of date) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.5-1ubuntu4 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G74Sx.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G74Sx 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.:bvrG74Sx.201:bd04/27/2011:svnASUSTeKComputerInc.:pnG74Sx:pvr1.0:rvnASUSTeKComputerInc.:rnG74Sx:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: G74Sx 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/firefox/+bug/1686568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
I've managed to fix partially the problem or at least I can narrow it down. So , if I override all my other audio lines via hdajackretask module and only enable the headphone one, the sound is perfect. What happens though when I turn back on the line for the Internal speakers , it goes back to crackling and popping in the internal speakers and headphones. So basically this allows the user to use EITHER internal speakers OR headphones , NOT both. -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685271] Re: gnome-shell: corners are not rounded
** Description changed: Under gnome-shell apps have dark black squared top corners when they should be rounded. See attached screenshot. + + See also bug 1685272 ** No longer affects: light-themes (Ubuntu) ** No longer affects: light-themes (Ubuntu Artful) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685271 Title: gnome-shell: corners are not rounded Status in ubuntu-themes package in Ubuntu: Triaged Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell apps have dark black squared top corners when they should be rounded. See attached screenshot. See also bug 1685272 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1685271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685272] Re: gnome-shell: no window border
I was initially content with the terse description "no window border" because I thought there was only this one bug covering the shadows and titlebar corner issues. But it turns out a second bug 1685271 exists for the latter. So yes, this bug now needs a better description... ** Summary changed: - gnome-shell: no window border + gnome-shell: no window shadows ** Description changed: - Under gnome-shell, there are no window borders. See attached + Under gnome-shell, there are no window borders (shadows). See attached screenshot. + + See also bug 1685271 ** No longer affects: light-themes (Ubuntu) ** No longer affects: light-themes (Ubuntu Artful) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685272 Title: gnome-shell: no window shadows Status in ubuntu-themes package in Ubuntu: Triaged Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell, there are no window borders (shadows). See attached screenshot. See also bug 1685271 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1685272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686573] [NEW] USB Modem not displayed in network manager
Public bug reported: 4G USB WAN modem will not display in network manager, but is fully detected by the kernel and is displayed in ip link journal; Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: new high-speed USB device number 5 using xhci_hcd Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has an invalid interface number: 7 but max is 3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has no interface number 2 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device found, idVendor=1199, idProduct=68a3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Product: AC760S Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Manufacturer: Sierra Wireless, Incorporated Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: SerialNumber: 359822042204515 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.0: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB0 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.1: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB1 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.3: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB2 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwan0: register 'sierra_net' at usb-:00:10.0-2, Sierra Wireless USB-to-WWAN Modem, ce:6b:97:53:02:07 Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: checking bus 5, device 5: "/sys/devices/pci:00/:00:10.0/usb5/5-2" Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: bus: 5, device: 5 was not an MTP device Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwp0s16f0u2i7: renamed from wwan0 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4733] devices added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4734] device added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7) Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB1): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB0): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Creating modem with plugin 'Sierra (legacy)' and '4' ports Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB1): 'Cannot add port 'tty/ttyUSB1', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Modem for device at '/sys/devices/pci:00/:00:10.0/usb5/5-2' successfully created Apr 27 10:57:01 Paul-HP-Laptop ModemManager[846]: Modem: state changed (unknown -> disabled) Apr 27 10:57:01 Paul-HP-Laptop NetworkManager[898]: [1493254621.9962] (ttyUSB2): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0002] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/5) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0043] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0065] device (ttyUSB2): modem state 'enabling' Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0080] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none') [20 30 0] Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling) Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering) Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home) Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered) Apr 27 10:57:06 Paul-HP-Laptop NetworkManager[898]: [1493254626.0016] (ttyUSB2): modem state changed, 'enabling' --> 'registered' (reason: user-requested) ip link; 6: wwp0s16f0u2i7: mtu 1500 qdisc noop state DOWN mode DEFAULT group default q
[Desktop-packages] [Bug 1686568] [NEW] Firefox Does Not Respond. Process can not be killed. Terminal commands to kill the process freeze. Logout Freeze.
Public bug reported: Firefox goes unresponsive occasionally after the latest kernel update. Can force-kill the window but the process can not be killed. Reboot stalls. Logout freezes the system. Must hard-reboot by long-pressing the power button to get back to normal and the same repeats randomly. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 53.0+build6-0ubuntu0.17.04.1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: murat 2753 F pulseaudio /dev/snd/controlC0: murat 2753 F pulseaudio BuildID: 20170418122848 Channel: Unavailable Date: Wed Apr 26 20:54:33 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 2016-01-26 (456 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto static metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.8 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=52.0.1/20170317212642 (Out of date) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.5-1ubuntu4 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G74Sx.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G74Sx 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.:bvrG74Sx.201:bd04/27/2011:svnASUSTeKComputerInc.:pnG74Sx:pvr1.0:rvnASUSTeKComputerInc.:rnG74Sx:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: G74Sx dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1686568 Title: Firefox Does Not Respond. Process can not be killed. Terminal commands to kill the process freeze. Logout Freeze. Status in firefox package in Ubuntu: New Bug description: Firefox goes unresponsive occasionally after the latest kernel update. Can force-kill the window but the process can not be killed. Reboot stalls. Logout freezes the system. Must hard-reboot by long-pressing the power button to get back to normal and the same repeats randomly. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 53.0+build6-0ubuntu0.17.04.1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: murat 2753 F pulseaudio /dev/snd/controlC0: murat 2753 F pulseaudio BuildID: 20170418122848 Channel: Unavailable Date: Wed Apr 26 20:54:33 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 2016-01-26 (456 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.0.1 dev enp5s0 proto static metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.8 metric 100 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profi
[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories
** Changed in: gnome-software (Ubuntu Yakkety) Status: Confirmed => Fix Committed ** Changed in: gnome-software (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Changed in: gnome-software (Ubuntu Yakkety) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Xenial) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1672424 Title: Cannot install Debian files outside of the repositories Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Bug description: Impact -- It is not possible to use the default Software app to install .debs for packages that are not already available in Ubuntu. Test Case - 1. a. Download the .deb for a simple app for your version of Ubuntu directly from Launchpad. For 16.10, try https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/ Click amd64 then download the last .deb on that page. b. Open the .deb with gnome-software: gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb gnome-software should open to a page with an Install button for the package. This test case should already work. 2. a. Download a .deb that is not already in Ubuntu. It is important that the package not be available in your local apt cache. For this, I made sure that I was not using the GNOME3 Staging PPA. As of today, switcheroo-control is not accepted into Ubuntu 17.04. So I downloaded https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+files /switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb b. Open the .deb with gnome-software gnome-software --local-filename=switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb I only suggested using switcheroo-control because I know it's not because the package isn't packaged correctly. Alternatively, this test case should also work with one of these: https://www.google.com/chrome/ https://itch.io/app gnome-software should open to a page with an Install button for the package. What Happens The second test fails. On Ubuntu 17.04, I get a popup "Sorry this did not work The file is not supported" On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No file_to_app results to show" Regression Potential Original Bug Report --- .deb files fail to install from non repository locations i.e. The file manager gnome-software claims "this file type is not supported". Using dpkg from the command line works as expected so the files aren't corrupt. This happened last distribution as well when it was first released. Might be a regression caused by adding snap package capabilities to the software-center? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 13 10:02:00 2017 InstallationDate: Installed on 2017-02-20 (20 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts
** Changed in: gnome-software (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Changed in: gnome-software (Ubuntu Xenial) Status: Triaged => Fix Committed -- 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/1679435 Title: GNOME Software fails to install .deb packages that trigger debconf prompts Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] GNOME Software doesn't provide debconf support when using aptd. This means any package installation / upgrade that triggers a debconf prompt can fail. The requested package might not do a prompt, but some dependency can. [Test Case] 1. Install a .deb file that causes a debconf prompt (https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test package). $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb Expected result: Package is installed after a debconf prompt is shown. Observed result: Package fails to install, no prompt is shown. [Regression Potential] The solution was to provide a pipe when using aptd to allow the debconf prompt to be handled in the session. This could introduce new bugs and/or security issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-yakkety ** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial -- 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/1672424 Title: Cannot install Debian files outside of the repositories Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Bug description: Impact -- It is not possible to use the default Software app to install .debs for packages that are not already available in Ubuntu. Test Case - 1. a. Download the .deb for a simple app for your version of Ubuntu directly from Launchpad. For 16.10, try https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/ Click amd64 then download the last .deb on that page. b. Open the .deb with gnome-software: gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb gnome-software should open to a page with an Install button for the package. This test case should already work. 2. a. Download a .deb that is not already in Ubuntu. It is important that the package not be available in your local apt cache. For this, I made sure that I was not using the GNOME3 Staging PPA. As of today, switcheroo-control is not accepted into Ubuntu 17.04. So I downloaded https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+files /switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb b. Open the .deb with gnome-software gnome-software --local-filename=switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb I only suggested using switcheroo-control because I know it's not because the package isn't packaged correctly. Alternatively, this test case should also work with one of these: https://www.google.com/chrome/ https://itch.io/app gnome-software should open to a page with an Install button for the package. What Happens The second test fails. On Ubuntu 17.04, I get a popup "Sorry this did not work The file is not supported" On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No file_to_app results to show" Regression Potential Original Bug Report --- .deb files fail to install from non repository locations i.e. The file manager gnome-software claims "this file type is not supported". Using dpkg from the command line works as expected so the files aren't corrupt. This happened last distribution as well when it was first released. Might be a regression caused by adding snap package capabilities to the software-center? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 13 10:02:00 2017 InstallationDate: Installed on 2017-02-20 (20 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-yakkety ** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial -- 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/1679435 Title: GNOME Software fails to install .deb packages that trigger debconf prompts Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Yakkety: Fix Committed Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] GNOME Software doesn't provide debconf support when using aptd. This means any package installation / upgrade that triggers a debconf prompt can fail. The requested package might not do a prompt, but some dependency can. [Test Case] 1. Install a .deb file that causes a debconf prompt (https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test package). $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb Expected result: Package is installed after a debconf prompt is shown. Observed result: Package fails to install, no prompt is shown. [Regression Potential] The solution was to provide a pipe when using aptd to allow the debconf prompt to be handled in the session. This could introduce new bugs and/or security issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
SB Recon3D Line Out does not work. I have a sound blaster zx running ubuntu 16.04 with kernerl 4.8.0 -46 My HDMI audio is working. I just plugged headphone in to the back of one of my monitors running and HDMI cord and sound is perfect... Would love to have my sound card working though -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538668] Re: No such file or directory: '~/.cache/oneconf/c4b2c66....00a0f7/other_hosts'
*** This bug is a duplicate of bug 1486450 *** https://bugs.launchpad.net/bugs/1486450 ** Also affects: oneconf Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to oneconf in Ubuntu. https://bugs.launchpad.net/bugs/1538668 Title: No such file or directory: '~/.cache/oneconf/c4b2c6600a0f7/other_hosts' Status in One Hundred Papercuts: Confirmed Status in OneConf: New Status in oneconf package in Ubuntu: Confirmed Bug description: journalctl has logged: com.ubuntu.OneConf[1780]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/oem/.cache/oneconf/c4b2c6660980c357474aa5a35400a0f7/other_hosts ls ~/.cache/oneconf/c4b2c6660980c357474aa5a35400a0f7/ package_list_c4b2c6660980c357474aa5a35400a0f7 host so other_hosts does not exist As this system is a single desktop, i suppose "other hosts" are not expected in such a case; so maybe simply silencing that check could be enough ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: oneconf 0.3.9 ProcVersionSignature: Ubuntu 4.4.0-1.15-generic 4.4.0 Uname: Linux 4.4.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jan 27 18:27:33 2016 PackageArchitecture: all SourcePackage: oneconf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1538668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
Bart van Deenan's solution worked for me under Ubuntu 16.10 but under 17.04 it seems to no longer fix the issue and headphones produce no sound. Dell XPS 15 9550 Ubuntu 17.04 4.10.0-20-generic -- 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/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686554] Re: package chromium-browser-l10n (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/ch
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1686554 Title: package chromium-browser-l10n (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium- browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak .dpkg-new': unexpected end of file or stream Status in chromium-browser package in Ubuntu: Invalid Bug description: tried to install but will not work ProblemType: Package DistroRelease: Ubuntu 14.04 Package: chromium-browser-l10n (not installed) ProcVersionSignature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-75-generic i686 ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: chromium-browser: Install chromium-browser-l10n: Install chromium-browser: Configure chromium-browser-l10n: Configure Architecture: i386 Date: Wed Apr 26 16:11:55 2017 DuplicateSignature: package:chromium-browser-l10n:(not installed):cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2017-04-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: chromium-browser Title: package chromium-browser-l10n (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1686554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686554] [NEW] package chromium-browser-l10n (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/
Public bug reported: tried to install but will not work ProblemType: Package DistroRelease: Ubuntu 14.04 Package: chromium-browser-l10n (not installed) ProcVersionSignature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-75-generic i686 ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: chromium-browser: Install chromium-browser-l10n: Install chromium-browser: Configure chromium-browser-l10n: Configure Architecture: i386 Date: Wed Apr 26 16:11:55 2017 DuplicateSignature: package:chromium-browser-l10n:(not installed):cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2017-04-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: chromium-browser Title: package chromium-browser-l10n (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-package corrupted-package i386 need-duplicate-check trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1686554 Title: package chromium-browser-l10n (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium- browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak .dpkg-new': unexpected end of file or stream Status in chromium-browser package in Ubuntu: Invalid Bug description: tried to install but will not work ProblemType: Package DistroRelease: Ubuntu 14.04 Package: chromium-browser-l10n (not installed) ProcVersionSignature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-75-generic i686 ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: chromium-browser: Install chromium-browser-l10n: Install chromium-browser: Configure chromium-browser-l10n: Configure Architecture: i386 Date: Wed Apr 26 16:11:55 2017 DuplicateSignature: package:chromium-browser-l10n:(not installed):cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2017-04-16 (10 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: chromium-browser Title: package chromium-browser-l10n (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium-browser/locales/kn.pak' to '/usr/lib/chromium-browser/locales/kn.pak.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1686554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1678498] Re: Resolution options for external display/monitor are incomplete
** Summary changed: - Resolution options for external monitor are incomplete + Resolution options for external display/monitor are incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1678498 Title: Resolution options for external display/monitor are incomplete Status in xorg package in Ubuntu: New Bug description: Usually when I plug in an external monitor (when awake, or before waking from suspend), my external display is rendered with 1024x768 resolution, and this is the highest resolution displayed by xrandr: DP-2 connected 1024x768+1920+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 But in fact if I reboot I get the full set of options back (1680x) for that monitor. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 1 12:17:13 2017 DistUpgraded: 2017-01-21 16:13:06,191 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2016-02-12 (413 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic.efi.signed root=UUID=ea2fb511-8d62-4b96-bdaa-4b3f7bf79cc6 ro noprompt quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2017-01-21 (69 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Apr 1 09:52:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644091] Re: restart of systemd unit transmission-daemon causes /etc/transmission-daemon/settings.json to be overwritten
> This seems to be fixed in 2.92-1ubuntu1. No, it's not, settings are still overwritten randomly after restarts of the service which makes absolutely no sense and is destructive. There's mentioning of that at https://thornelabs.net/2013/08/18 /transmission-settings-json-reverting-to-defaults.html as well including workaround suggestions. ** Changed in: transmission (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1644091 Title: restart of systemd unit transmission-daemon causes /etc/transmission- daemon/settings.json to be overwritten Status in transmission package in Ubuntu: New Bug description: Restart of systemd unit transmission-daemon causes /etc/transmission- daemon/settings.json to be overwritten. That doesn't make sense and the warning in the sibling file README.md is an unnecessary complication because it can easily be a comment in settings.json itself. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: transmission-daemon 2.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Nov 23 06:56:40 2016 InstallationDate: Installed on 2015-04-20 (582 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to yakkety on 2016-10-19 (34 days ago) modified.conffile..etc.transmission-daemon.settings.json: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/transmission-daemon/settings.json'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1644091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1644091] Re: restart of systemd unit transmission-daemon causes /etc/transmission-daemon/settings.json to be overwritten
This seems to be fixed in 2.92-1ubuntu1. ** Changed in: transmission (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1644091 Title: restart of systemd unit transmission-daemon causes /etc/transmission- daemon/settings.json to be overwritten Status in transmission package in Ubuntu: Fix Released Bug description: Restart of systemd unit transmission-daemon causes /etc/transmission- daemon/settings.json to be overwritten. That doesn't make sense and the warning in the sibling file README.md is an unnecessary complication because it can easily be a comment in settings.json itself. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: transmission-daemon 2.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Nov 23 06:56:40 2016 InstallationDate: Installed on 2015-04-20 (582 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to yakkety on 2016-10-19 (34 days ago) modified.conffile..etc.transmission-daemon.settings.json: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/transmission-daemon/settings.json'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1644091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories
This bug was fixed in the package gnome-software - 3.22.7-0ubuntu4 --- gnome-software (3.22.7-0ubuntu4) artful; urgency=medium * debian/patches/0002-Add-an-APT-plugin.patch: - Support debconf prompts (LP: #1679435) * debian/patches/0015-dpkg-Mark-local-.debs-as-managed-by-APT.patch: * debian/patches/0016-Make-filename-passed-with-local-filename-absolute.patch: - Fix local .deb files not being installable: (LP: #1672424) -- Robert Ancell Wed, 26 Apr 2017 15:47:47 +1200 ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- 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/1672424 Title: Cannot install Debian files outside of the repositories Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Confirmed Status in gnome-software source package in Yakkety: Confirmed Status in gnome-software source package in Zesty: Fix Committed Bug description: Impact -- It is not possible to use the default Software app to install .debs for packages that are not already available in Ubuntu. Test Case - 1. a. Download the .deb for a simple app for your version of Ubuntu directly from Launchpad. For 16.10, try https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/ Click amd64 then download the last .deb on that page. b. Open the .deb with gnome-software: gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb gnome-software should open to a page with an Install button for the package. This test case should already work. 2. a. Download a .deb that is not already in Ubuntu. It is important that the package not be available in your local apt cache. For this, I made sure that I was not using the GNOME3 Staging PPA. As of today, switcheroo-control is not accepted into Ubuntu 17.04. So I downloaded https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+files /switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb b. Open the .deb with gnome-software gnome-software --local-filename=switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb I only suggested using switcheroo-control because I know it's not because the package isn't packaged correctly. Alternatively, this test case should also work with one of these: https://www.google.com/chrome/ https://itch.io/app gnome-software should open to a page with an Install button for the package. What Happens The second test fails. On Ubuntu 17.04, I get a popup "Sorry this did not work The file is not supported" On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No file_to_app results to show" Regression Potential Original Bug Report --- .deb files fail to install from non repository locations i.e. The file manager gnome-software claims "this file type is not supported". Using dpkg from the command line works as expected so the files aren't corrupt. This happened last distribution as well when it was first released. Might be a regression caused by adding snap package capabilities to the software-center? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 13 10:02:00 2017 InstallationDate: Installed on 2017-02-20 (20 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts
This bug was fixed in the package gnome-software - 3.22.7-0ubuntu4 --- gnome-software (3.22.7-0ubuntu4) artful; urgency=medium * debian/patches/0002-Add-an-APT-plugin.patch: - Support debconf prompts (LP: #1679435) * debian/patches/0015-dpkg-Mark-local-.debs-as-managed-by-APT.patch: * debian/patches/0016-Make-filename-passed-with-local-filename-absolute.patch: - Fix local .deb files not being installable: (LP: #1672424) -- Robert Ancell Wed, 26 Apr 2017 15:47:47 +1200 ** Changed in: gnome-software (Ubuntu Artful) Status: Fix Committed => Fix Released -- 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/1679435 Title: GNOME Software fails to install .deb packages that trigger debconf prompts Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Yakkety: Triaged Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] GNOME Software doesn't provide debconf support when using aptd. This means any package installation / upgrade that triggers a debconf prompt can fail. The requested package might not do a prompt, but some dependency can. [Test Case] 1. Install a .deb file that causes a debconf prompt (https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test package). $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb Expected result: Package is installed after a debconf prompt is shown. Observed result: Package fails to install, no prompt is shown. [Regression Potential] The solution was to provide a pipe when using aptd to allow the debconf prompt to be handled in the session. This could introduce new bugs and/or security issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories
** Changed in: gnome-software (Ubuntu Zesty) Status: Confirmed => Fix Committed -- 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/1672424 Title: Cannot install Debian files outside of the repositories Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: Confirmed Status in gnome-software source package in Yakkety: Confirmed Status in gnome-software source package in Zesty: Fix Committed Bug description: Impact -- It is not possible to use the default Software app to install .debs for packages that are not already available in Ubuntu. Test Case - 1. a. Download the .deb for a simple app for your version of Ubuntu directly from Launchpad. For 16.10, try https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/ Click amd64 then download the last .deb on that page. b. Open the .deb with gnome-software: gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb gnome-software should open to a page with an Install button for the package. This test case should already work. 2. a. Download a .deb that is not already in Ubuntu. It is important that the package not be available in your local apt cache. For this, I made sure that I was not using the GNOME3 Staging PPA. As of today, switcheroo-control is not accepted into Ubuntu 17.04. So I downloaded https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+files /switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb b. Open the .deb with gnome-software gnome-software --local-filename=switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb I only suggested using switcheroo-control because I know it's not because the package isn't packaged correctly. Alternatively, this test case should also work with one of these: https://www.google.com/chrome/ https://itch.io/app gnome-software should open to a page with an Install button for the package. What Happens The second test fails. On Ubuntu 17.04, I get a popup "Sorry this did not work The file is not supported" On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No file_to_app results to show" Regression Potential Original Bug Report --- .deb files fail to install from non repository locations i.e. The file manager gnome-software claims "this file type is not supported". Using dpkg from the command line works as expected so the files aren't corrupt. This happened last distribution as well when it was first released. Might be a regression caused by adding snap package capabilities to the software-center? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-software 3.22.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 13 10:02:00 2017 InstallationDate: Installed on 2017-02-20 (20 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts
** Description changed: - i was installing stuff from the software center + [Impact] + GNOME Software doesn't provide debconf support when using aptd. This means any package installation / upgrade that triggers a debconf prompt can fail. The requested package might not do a prompt, but some dependency can. - ProblemType: Package - DistroRelease: Ubuntu 16.10 - Package: shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 - ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 - Uname: Linux 4.8.0-45-generic x86_64 - ApportVersion: 2.20.3-0ubuntu8.2 - Architecture: amd64 - Date: Mon Apr 3 18:51:34 2017 - DuplicateSignature: - package:shim-signed:1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 - Processing triggers for shim-signed (1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1) ... - Running in non-interactive mode, doing nothing. - dpkg: error processing package shim-signed (--configure): - subprocess installed post-installation script returned error exit status 1 - ErrorMessage: subprocess installed post-installation script returned error exit status 1 - InstallationDate: Installed on 2017-04-03 (0 days ago) - InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) - RelatedPackageVersions: - dpkg 1.18.10ubuntu1 - apt 1.3.4 - SourcePackage: shim-signed - Title: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - UpgradeStatus: No upgrade log present (probably fresh install) + [Test Case] + 1. Install a .deb file that causes a debconf prompt (https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test package). + $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb + + Expected result: + Package is installed after a debconf prompt is shown. + + Observed result: + Package fails to install, no prompt is shown. + + [Regression Potential] + The solution was to provide a pipe when using aptd to allow the debconf prompt to be handled in the session. This could introduce new bugs and/or security issues. -- 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/1679435 Title: GNOME Software fails to install .deb packages that trigger debconf prompts Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Yakkety: Triaged Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Committed Bug description: [Impact] GNOME Software doesn't provide debconf support when using aptd. This means any package installation / upgrade that triggers a debconf prompt can fail. The requested package might not do a prompt, but some dependency can. [Test Case] 1. Install a .deb file that causes a debconf prompt (https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test package). $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb Expected result: Package is installed after a debconf prompt is shown. Observed result: Package fails to install, no prompt is shown. [Regression Potential] The solution was to provide a pipe when using aptd to allow the debconf prompt to be handled in the session. This could introduce new bugs and/or security issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts
** Summary changed: - installing dkms package from gnome-software, no debconf frontend: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 + GNOME Software fails to install .deb packages that trigger debconf prompts ** No longer affects: shim-signed (Ubuntu) ** Also affects: gnome-software (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Artful) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Fix Committed ** Also affects: gnome-software (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Zesty) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Yakkety) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Zesty) Status: Triaged => Fix Committed ** Changed in: gnome-software (Ubuntu Zesty) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Yakkety) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Xenial) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1679435 Title: GNOME Software fails to install .deb packages that trigger debconf prompts Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Yakkety: Triaged Status in gnome-software source package in Zesty: Fix Committed Status in gnome-software source package in Artful: Fix Committed Bug description: [Impact] GNOME Software doesn't provide debconf support when using aptd. This means any package installation / upgrade that triggers a debconf prompt can fail. The requested package might not do a prompt, but some dependency can. [Test Case] 1. Install a .deb file that causes a debconf prompt (https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test package). $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb Expected result: Package is installed after a debconf prompt is shown. Observed result: Package fails to install, no prompt is shown. [Regression Potential] The solution was to provide a pipe when using aptd to allow the debconf prompt to be handled in the session. This could introduce new bugs and/or security issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686522] [NEW] Network Manager frequently disconnects wlan0
Public bug reported: In syslog there are multiple lines: wlan0: CTRL-EVENT-DISCONNECTED reason=4 locally_generated=1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.3 ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39 Uname: Linux 3.13.0-117-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Wed Apr 26 16:56:26 2017 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-27 (242 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_IE:en TERM=linux PATH=(custom, no user) LANG=en_IE.UTF-8 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1686522 Title: Network Manager frequently disconnects wlan0 Status in network-manager package in Ubuntu: New Bug description: In syslog there are multiple lines: wlan0: CTRL-EVENT-DISCONNECTED reason=4 locally_generated=1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.3 ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39 Uname: Linux 3.13.0-117-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Wed Apr 26 16:56:26 2017 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-27 (242 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_IE:en TERM=linux PATH=(custom, no user) LANG=en_IE.UTF-8 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1686522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 611590] Re: Brasero keeps on asking for libdvdcss.so.2
*** This bug is a duplicate of bug 1577268 *** https://bugs.launchpad.net/bugs/1577268 ** This bug has been marked a duplicate of bug 1577268 Brasero can't find libdvdcss when going from Ubuntu 14.04 to 16.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/611590 Title: Brasero keeps on asking for libdvdcss.so.2 Status in brasero package in Ubuntu: Confirmed Bug description: Binary package hint: brasero I added the medibuntu sources and installed the libdvdcss2 package. Output of locate: doogej@WVUN002:/$ sudo locate libdvdcss /home/doogej/VMShared/brasero_libdvdcss.png /usr/lib/libdvdcss.so.2 /usr/lib/libdvdcss.so.2.1.0 /usr/share/app-install/desktop/libdvdcss.desktop /usr/share/doc/libdvdcss2 /usr/share/doc/libdvdcss2/NEWS.gz /usr/share/doc/libdvdcss2/README /usr/share/doc/libdvdcss2/changelog.Debian.gz /usr/share/doc/libdvdcss2/changelog.gz /usr/share/doc/libdvdcss2/copyright /var/cache/apt/archives/libdvdcss2_1.2.10-0.3medibuntu1_amd64.deb /var/lib/dpkg/info/libdvdcss2.list /var/lib/dpkg/info/libdvdcss2.md5sums /var/lib/dpkg/info/libdvdcss2.postinst /var/lib/dpkg/info/libdvdcss2.postrm /var/lib/dpkg/info/libdvdcss2.shlibs Too bad Brasero keeps on 'whining' about missing this file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/611590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577268] Re: Brasero can't find libdvdcss when going from Ubuntu 14.04 to 16.04
** This bug is no longer a duplicate of bug 611590 Brasero keeps on asking for libdvdcss.so.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1577268 Title: Brasero can't find libdvdcss when going from Ubuntu 14.04 to 16.04 Status in brasero package in Ubuntu: Fix Released Status in brasero source package in Xenial: Fix Released Bug description: * Impact the libcss plugin can't be enable with the current libdvdcss version * Test case - install libdvdcss - start brasero - go to the plugins dialog, enable the libdvdcss plugin * Regression potential none, the plugin was not loading at all and it's only its loader being changed "I recently updated one of my rigs from 14.04 to 16.04. After upgrading Brasero tells me that it can't find libdvdcss. VLC play an inserted DVD, I see libdvdcss in /usr/lib/x86_64-linux gnu. However, i didn't see it simply in /usr/lib/ so I created a link there. Still didn't work, so I copied an older libdvdcss to /usr/lib. Still no joy. I checked to see what versions of libdvdcss I had installed - 2.2.0 in /usr/lib/x86_64-linux, 2.1.0 in /usr/lib * mv'ed the.2.1.0 to x86_64-linux * rm'ed the sym links to 2.2.0 * new sym link to 2.1.0 * works. " Originally reported here : https://www.reddit.com/r/Ubuntu/comments/4h4pcn/anybody_using_brasero_to_rip_dvds_in_1604/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1577268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 864735] Re: [ATI HDMI] HDMI Audio Disabled by Default (since oneiric)
This problem has shown up in 16.04 with alsamixer v1.1.0. Did someone remove the patch or fail to integrate the fix into 16.04 had to run alsamixer from terminal and unmute the speaker from there. Muting and un-muting in rhythem box does not fix the HDMI sound problem. -- 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/864735 Title: [ATI HDMI] HDMI Audio Disabled by Default (since oneiric) Status in alsa-driver package in Ubuntu: Fix Released Bug description: Since kernel 3.0, upstream has disabled audio output for all ATI cards in the Radeon driver by default. === Workaround 1 === Edit /etc/default/grub and change this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to this line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.audio=1" Now run "sudo update-grub", then reboot your computer. === Or workaround 2 === Install the proprietary Catalyst driver. === There's no sound at all and videos playback in fast forward when outputting through the HDMI controller. This is a regression since it worked well in previous releases. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: melvin 8335 F pulseaudio /dev/snd/pcmC1D3p: melvin 8335 F...m pulseaudio /dev/snd/controlC0: melvin 8335 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe6f4000 irq 16' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10ec0888,00100101' Controls : 38 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sun Oct 2 12:46:40 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110929) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: RS780 Azalia controller - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [GT5676, ATI RS690/780 HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7B3G1P04 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Not Available dmi.board.vendor: Gateway dmi.board.version: Not Available dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7B3G1P04:bd02/18/2008:svnGateway:pnGT5676:pvr7B3G1P04:rvnGateway:rnNotAvailable:rvrNotAvailable:cvnGateway:ct3:cvr1.0: dmi.product.name: GT5676 dmi.product.version: 7B3G1P04 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/864735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684100] Re: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10
The workaround fixes it for me too. Other wifi adapters I have (one using rt73usb, the other rtl8812au) don't need it, so maybe the bug lies in athk9_htc. How did you find the workaround? (just curious, apart from this bug my google searches only gave me outdated or irrelevant information). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1684100 Title: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10 Status in gnome-nettool package in Ubuntu: Confirmed Bug description: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10 sudo apt-get update; sudo apt-get install usbutils pciutils hwinfo grep rfkill; sudo lshw -C network; rfkill list; sudo iwlist scan | grep -Ei 'chan|ssid'; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | grep -iA2 net; lsusb; nmcli nm status; sudo lshw -short; uname -a; sudo updatedb; dmesg | grep -E '02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|RTL|rt2|RT2|rt3|RT3|rt5|RT5|rt6|RT6|rt7|RT7|usb|witch|wl';sudo dmidecode|grep -E 'anufact|roduct|erial|elease'; iwconfig; grep -E '80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl' /etc/modprobe.d/*; cat /var/lib/NetworkManager/NetworkManager.state; sudo hwinfo --netcard ; ps -aux|grep -E 'wpa|icd|etwork'; netstat -rn ; cat /etc/resolv.conf; ls -lia /boot; grep tmpfs /etc/fstab; ubuntu-support-status; sudo update-pciids; sudo update-usbids; sudo lsmod Get:1 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu zesty InRelease [243 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB] Hit:4 http://gb.archive.ubuntu.com/ubuntu zesty-backports InRelease Fetched 421 kB in 0s (873 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done grep is already the newest version (2.27-2). pciutils is already the newest version (1:3.3.1-1.1ubuntu9). pciutils set to manually installed. rfkill is already the newest version (0.5-1ubuntu3). rfkill set to manually installed. usbutils is already the newest version (1:007-4). usbutils set to manually installed. The following additional packages will be installed: libhd21 libx86emu1 The following NEW packages will be installed hwinfo libhd21 libx86emu1 0 to upgrade, 3 to newly install, 0 to remove and 0 not to upgrade. Need to get 754 kB of archives. After this operation, 3,261 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libx86emu1 amd64 1.11-2 [47.8 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libhd21 amd64 21.38-1 [688 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 hwinfo amd64 21.38-1 [17.7 kB] Fetched 754 kB in 0s (2,074 kB/s) Selecting previously unselected package libx86emu1:amd64. (Reading database ... 177811 files and directories currently installed.) Preparing to unpack .../libx86emu1_1.11-2_amd64.deb ... Unpacking libx86emu1:amd64 (1.11-2) ... Selecting previously unselected package libhd21:amd64. Preparing to unpack .../libhd21_21.38-1_amd64.deb ... Unpacking libhd21:amd64 (21.38-1) ... Selecting previously unselected package hwinfo. Preparing to unpack .../hwinfo_21.38-1_amd64.deb ... Unpacking hwinfo (21.38-1) ... Setting up libx86emu1:amd64 (1.11-2) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up libhd21:amd64 (21.38-1) ... Setting up hwinfo (21.38-1) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 06 serial: f4:6d:04:90:cb:7a size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:31 ioport:c000(size=256) memory:f0004000-f0004fff memory:f000-f0003fff *-network:0 description: Wireless interface physical id: 3 bus in
[Desktop-packages] [Bug 1684100] Re: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-nettool (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1684100 Title: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10 Status in gnome-nettool package in Ubuntu: Confirmed Bug description: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10 sudo apt-get update; sudo apt-get install usbutils pciutils hwinfo grep rfkill; sudo lshw -C network; rfkill list; sudo iwlist scan | grep -Ei 'chan|ssid'; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | grep -iA2 net; lsusb; nmcli nm status; sudo lshw -short; uname -a; sudo updatedb; dmesg | grep -E '02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|RTL|rt2|RT2|rt3|RT3|rt5|RT5|rt6|RT6|rt7|RT7|usb|witch|wl';sudo dmidecode|grep -E 'anufact|roduct|erial|elease'; iwconfig; grep -E '80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl' /etc/modprobe.d/*; cat /var/lib/NetworkManager/NetworkManager.state; sudo hwinfo --netcard ; ps -aux|grep -E 'wpa|icd|etwork'; netstat -rn ; cat /etc/resolv.conf; ls -lia /boot; grep tmpfs /etc/fstab; ubuntu-support-status; sudo update-pciids; sudo update-usbids; sudo lsmod Get:1 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu zesty InRelease [243 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB] Hit:4 http://gb.archive.ubuntu.com/ubuntu zesty-backports InRelease Fetched 421 kB in 0s (873 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done grep is already the newest version (2.27-2). pciutils is already the newest version (1:3.3.1-1.1ubuntu9). pciutils set to manually installed. rfkill is already the newest version (0.5-1ubuntu3). rfkill set to manually installed. usbutils is already the newest version (1:007-4). usbutils set to manually installed. The following additional packages will be installed: libhd21 libx86emu1 The following NEW packages will be installed hwinfo libhd21 libx86emu1 0 to upgrade, 3 to newly install, 0 to remove and 0 not to upgrade. Need to get 754 kB of archives. After this operation, 3,261 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libx86emu1 amd64 1.11-2 [47.8 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libhd21 amd64 21.38-1 [688 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 hwinfo amd64 21.38-1 [17.7 kB] Fetched 754 kB in 0s (2,074 kB/s) Selecting previously unselected package libx86emu1:amd64. (Reading database ... 177811 files and directories currently installed.) Preparing to unpack .../libx86emu1_1.11-2_amd64.deb ... Unpacking libx86emu1:amd64 (1.11-2) ... Selecting previously unselected package libhd21:amd64. Preparing to unpack .../libhd21_21.38-1_amd64.deb ... Unpacking libhd21:amd64 (21.38-1) ... Selecting previously unselected package hwinfo. Preparing to unpack .../hwinfo_21.38-1_amd64.deb ... Unpacking hwinfo (21.38-1) ... Setting up libx86emu1:amd64 (1.11-2) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up libhd21:amd64 (21.38-1) ... Setting up hwinfo (21.38-1) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 06 serial: f4:6d:04:90:cb:7a size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:31 ioport:c000(size=256) memory:f0004000-f0004fff memory:f000-f0003fff *-network:0 description: Wireless interface physical id: 3 bus info: usb@2:1.7 logical name: wlxf81a6721bb82 serial: 56:3e:54:48:50:00 capabilities: ethernet physical wireless config
[Desktop-packages] [Bug 1686500] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Just doing a new upgrade install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 11:42:04 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-06-22 (307 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-04-26 (0 days ago) ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1686500 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: Just doing a new upgrade install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 11:42:04 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-06-22 (307 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1686500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes
Hello, I am also affected. Ubuntu 16.04 network-manager-openvpn-gnome 1.1.93-1ubuntu1.1 The same config file used from bash, works fine, in GUI ignores most of pushed routes. There are lots logs like: Apr 26 20:54:21 dell NetworkManager[1170]: [1493232861.9544] vpn-connection[blabla,"vpn",20:(tun0)]: Data: Static Route: 10.42.0.0/16 Next Hop: 10.8.0.4 9 But finally routing table is not changed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1603600 Title: NetworkManager ignores pushed openvpn routes Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Relevant information that may or may not have been included by ubuntu- bug: Ubuntu release 16.04 Package network-manager 1.2.0-0ubuntu0.16.04.2 Package network-manager-openvpn 1.1.93-1ubuntu1 NetworkManager ignores pushed openvpn routes when "Use this connection only for resources on its network" is checked. This is a behavior change since 14.04. To repeat: 1) Use an OpenVpn server that pushes routes. I suggest using a server that pushes several routes since this makes their absence obvious. Set up a NetworkManager VPN of type OpenVpn to this server. Select "Use this connection only for resources on its network" in the "Routes" section of the IPV4 options. 2) Set up a raw OpenVpn connection to the same server. 3) Connect to the server using the raw OpenVpn connection. The pushed routes are all there. 4) Connect to the server using NetworkManager. The only route added is a n interface level route to the tunnel device network. Using the same setup on 14.04, all pushed routes are added. The missing routes are also "Resources on the VPN network", and should be added in the absence of further direction. Ignoring pushed routes should be controlled by the "Ignore automatically obtained routes" checkbox. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jul 15 23:12:55 2016 InstallationDate: Installed on 2016-05-04 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1459235] Re: Google Address book: Unable to open address book
Somehow on the version of Evolution 3.22.6 that I am using when adding a google account it allowed me to sign in to google and authorize the adding of the account. This was after installing account-plugin-google on Kubuntu 17.04. I'm not 100% sure that helped but I figured it might after searching the packages for google. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1459235 Title: Google Address book: Unable to open address book Status in evolution package in Ubuntu: Confirmed Bug description: Since today (2015-05-27) I've been getting this message when trying to open my Google address book: Unable to open address book This address book cannot be opened. This either means that an incorrect URI was entered, or the server is unreachable. Detailed error message: Unable to connect to 'Google address book': The requested resource was not found: https://developers.google.com/accounts/docs/AuthForInstalledApps Running standard Evolution ( 3.10.4) on Ubuntu 14.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1459235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1533480] Re: banshee stops respondiing during media import
Banshee running on zesty, 22k tracks, disabled all extensions, still crashing on importing files or folders. Problem was not present under yakkety. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1533480 Title: banshee stops respondiing during media import Status in banshee package in Ubuntu: Confirmed Bug description: Trying to import media to banshee in ubuntu 16.04 freezes banshee. Import works fine in rhythmbox. Problem only with banshee ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.3.0-5-generic 4.3.0-5.16 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krishnan 1972 F pulseaudio /dev/snd/controlC0: krishnan 1972 F pulseaudio Date: Wed Jan 13 10:20:16 2016 HibernationDevice: RESUME=UUID=1f4f89ff-6e3c-4610-8450-a25509f5b5c5 InstallationDate: Installed on 2015-12-26 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) MachineType: LENOVO INVALID ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic.efi.signed root=UUID=0bf37a84-dc7d-4bd4-999a-f8df2baffc39 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.3.0-5-generic N/A linux-backports-modules-4.3.0-5-generic N/A linux-firmware 1.155 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN12WW(V1.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.name: INVALID dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1533480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586787] Re: Wrong colors on external TV
I managed to solve my issue: I found a passive DisplayPort to HDMI adapter that works (the colors on the TV are as expected). But I still think that there is a software issue, or an issue that ca be solved with software, since with the exact same hardware the colors are fine with certain software. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1586787 Title: Wrong colors on external TV Status in xorg package in Ubuntu: New Bug description: Hi, On a Lenovo Thinkpad T420, with an Intel Core i5-2520M CPU and integrated graphics, when using a Samsung UE40J5200AW 40in TV with a DisplayPort to HDMI adapter and an HDMI cable, the colors are very wrong on the TV. This happens on a brand new Ubuntu 16.04 installation made from scratch, and it does not happen when I boot from a Linux Mint 17.3 "Rosa" Cinnamon 64-bit live DVD. So same laptop, same adapter, same cable, same TV, and the colors are fine on the TV in this case (Mint live DVD). Also, when switching the laptop with a Dell running Windows 8.1 (so the same adapter, cable, and TV are used), the colors are again fine. I have attached a picture that shows the laptop screen in front of the TV screen with the display mirrored. So both screens should look the same in the picture. But it looks like only the white color is the same, while the rest of the colors are very different. Thanks for your help, Alin. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 29 17:47:11 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21ce] InstallationDate: Installed on 2016-05-06 (22 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 4236BH1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236BH1 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:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236BH1:pvrThinkPadT420:rvnLENOVO:rn4236BH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236BH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 29 17:45:29 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 738 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
Issue definitely persists on 4.11/upstream. I came across an interesting output in dmesg which may explain why bluetooth works while the WiFi doesn't: [17326.525545] iwlwifi :01:00.0: Could not load the [0] uCode section [17326.525697] iwlwifi :01:00.0: Failed to start INIT ucode: -5 [17326.525702] iwlwifi :01:00.0: Failed to run INIT ucode: -5 [17326.525705] iwlwifi :01:00.0: Failed to start RT ucode: -5 [17391.638774] usb 1-4: USB disconnect, device number 64 [17392.015275] usb 1-4: new full-speed USB device number 65 using xhci_hcd [17392.156505] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc [17392.156520] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [17392.179288] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [17392.179426] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [17392.367199] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated What's interesting is that iwlwifi "can't load" the uCode/firmware, causing the internet/wifi portion to fail, but Bluetooth uses a separate firmware file on the same card, which itself works fine. So this probably explains why the bluetooth still works. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.p
[Desktop-packages] [Bug 1591547] Re: Merge pcsc-lite 1.8.20-1 (main) from Debian testing (main)
Ping! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1591547 Title: Merge pcsc-lite 1.8.20-1 (main) from Debian testing (main) Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Please merge pcsc-lite 1.8.20-1 (main) from Debian testing (main) for bugs and security fixes. --- 1.8.20: Ludovic Rousseau 30 December 2016 - Fix a crash and potential security issue in pcscd 1.8.19: Ludovic Rousseau 9 December 2016 - SCardGetStatusChange(): Fix a (rare) race condition - Doxygen: . SCardGetStatusChange() may return SCARD_E_UNKNOWN_READER . SCardConnect() and SCardReconnect() will never return SCARD_E_NOT_READY - pcsc-spy: . fix display of execution time . log the thread number in the results - Some other minor improvements 1.8.18: Ludovic Rousseau 10 August 2016 - SCardDisconnect(): much faster with SCARD_UNPOWER_CARD - SCardConnect(): Fix a possible duplicated hCard context - Fix compilation on FreeBSD - Fix compilation on Solaris - Some other minor improvements 1.8.17: Ludovic Rousseau 29 May 2016 - Fix SCardEndTransaction() issue with a SCARD_SHARE_EXCLUSIVE connection - Fix an issue when used with systemd (problem in signal handler) - SCardGetAttrib(): set pcbAttrLen when buffer is too small - Doxygen: SCardGetAttrib() pbAttr can be NULL - Doxygen: SCardGetAttrib() *pcbAttrLen contains the buffer size - fix compilation warnings and link errors on SunOS - Some other minor improvements 1.8.16: Ludovic Rousseau 20 March 2016 - SCardCancel() was not correctly handled When a SCardGetStatusChange() was cancelled then a next PC/SC call after the SCardGetStatusChange() may fail with a strange error code if the event waited in SCardGetStatusChange() occurs. - Doxygen: fix different documentation issues - SCARD_SCOPE_GLOBAL is now defined in a public header (even if never used) - Enable Trace and Profile features using compiler flags and without modifying the source code - Some other minor improvements and bug corrections 1.8.15: Ludovic Rousseau 25 December 2015 - Add support of remove and/or customize PC/SC reader names using PCSCLITE_FILTER_IGNORE_READER_NAMES and PCSCLITE_FILTER_EXTEND_READER_NAMES See http://ludovicrousseau.blogspot.fr/2015/12/remove-andor-customize-pcsc-reader-names.html - Some other minor improvements and bug corrections - Explanation of the Ubuntu delta: * Merge new upstream release from Debian Unstable (LP: #1483750). - debian/rules: Move runtime libraries to /lib, for the benefit of wpasupplicant. (See Debian #531592) Sorry, my packaging skills are zero, so that I can't work on this merge. - Changelog entries since current yakkety version 1.8.14-1ubuntu1: pcsc-lite (1.8.20-1) unstable; urgency=medium * New upstream release -- Ludovic Rousseau Fri, 30 Dec 2016 18:17:58 +0100 pcsc-lite (1.8.19-1) unstable; urgency=medium * New upstream release -- Ludovic Rousseau Fri, 09 Dec 2016 10:11:15 +0100 pcsc-lite (1.8.18-1) unstable; urgency=medium * New upstream release -- Ludovic Rousseau Wed, 10 Aug 2016 20:56:54 +0200 pcsc-lite (1.8.17-1) unstable; urgency=medium * New upstream release * debian/control: Standards-Version: 3.9.7 -> 3.9.8. No change needed. -- Ludovic Rousseau Sun, 29 May 2016 17:30:12 +0200 pcsc-lite (1.8.16-1) unstable; urgency=medium * New upstream release * debian/control: fix lintian warning vcs-field-uses-insecure-uri vcs-browser Use https:// instead of http:// * debian/control: Standards-Version: 3.9.6 -> 3.9.7. No change needed. * debian/rules: use "hardening=+all" to harden even more the binaries -- Ludovic Rousseau Sun, 20 Mar 2016 17:28:29 +0100 pcsc-lite (1.8.15-1) unstable; urgency=medium * New upstream release -- Ludovic Rousseau Fri, 25 Dec 2015 21:28:30 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1591547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 211632] Re: vlc does not play files from a "bookmarked" smb share
No. I can confirm. SFTP (basically SSH) mounts from nautilus can be opened from vlc, but not FTP and possibly SMB as well. With FTP mount the symptoms are exactly as https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/211632/comments/9 -- 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/211632 Title: vlc does not play files from a "bookmarked" smb share Status in gvfs package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in vlc package in Ubuntu: Fix Released Bug description: When using Nautilus to create shares to a NAS box, using smbfs/cifs, vlc will not play the files saying that it does not have smb:// support. I believe that vlc actually supports it, but it seems that it is not on by default in Hardy Beta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/211632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686473] [NEW] Won't start in 17.04. Terminal gives error
Public bug reported: After a fresh install of Rhythmbox, trying to run from the app launcher in GNOME desktop results in the attempted-opening-rhythmbox instance unresponsive. After ten or fifteen seconds, it says this program has failed to respond, and asks me to Wait or Force Quit the program. Running from Terminal produces the following: (rhythmbox:8731): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files BUG DISCOVERED USING: Ubuntu GNOME 17.04 x64 GNOME 3.24.0 desktop environment Xorg 7.7 session Linux kernel 4.10.0-20-generic Rhythmbox version 3.4.1-2ubuntu1 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1686473 Title: Won't start in 17.04. Terminal gives error Status in rhythmbox package in Ubuntu: New Bug description: After a fresh install of Rhythmbox, trying to run from the app launcher in GNOME desktop results in the attempted-opening-rhythmbox instance unresponsive. After ten or fifteen seconds, it says this program has failed to respond, and asks me to Wait or Force Quit the program. Running from Terminal produces the following: (rhythmbox:8731): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files BUG DISCOVERED USING: Ubuntu GNOME 17.04 x64 GNOME 3.24.0 desktop environment Xorg 7.7 session Linux kernel 4.10.0-20-generic Rhythmbox version 3.4.1-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1686473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708704] Re: Notifications inconsistent with other Ubuntu notifications
Probably. However I just tested on unity7 and no notification shows up. This seems to work only in gnome-shell. So not something that can be enabled by default for now. ** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708704 Title: Notifications inconsistent with other Ubuntu notifications Status in chromium-browser package in Ubuntu: Confirmed Bug description: Binary package hint: chromium-browser Today gmail/chromium told me I can get desktop notifications on new emails, which is a great feature. Unfortunately the notifications don't use the Ubuntu notifications APIs (libnotify?) and seem out of place. There was apparently some discussion on the Ayatana mailing list, but there didn't seem to be a conclusion. I think chromium on Ubuntu should use the existing infrastructure even if that results in some loss of features (HTML and interactivity) compared to other platforms. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 8.0.552.237~r70801-0ubuntu1~ucd~stable2~maverick ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 CrashDB: ubuntu Date: Thu Jan 27 17:43:02 2011 Desktop-Session: DESKTOP_SESSION = gnome GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686471] [NEW] system settings freezes
Public bug reported: whenever i try to open system settings the entire system freezes for a few seconds . only thing i can do is move the mouse pointer but cannot click on anything. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Apr 26 22:43:24 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1686471 Title: system settings freezes Status in unity-control-center package in Ubuntu: New Bug description: whenever i try to open system settings the entire system freezes for a few seconds . only thing i can do is move the mouse pointer but cannot click on anything. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Apr 26 22:43:24 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1686471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 I was also affected by this after doing a release upgrade of my system. Very very annoying and I was searching for ever until I found this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1664147] Re: Chromium on trusty too outdated; not supported by gmail
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1664147 Title: Chromium on trusty too outdated; not supported by gmail Status in chromium-browser package in Ubuntu: Fix Released Bug description: As of Feb 13 2017, the chromium version on trusty is 53.x which is at least a couple of versions behind chrome-stable. Gmail displays this message, "This version of Chrome is no longer supported. Please upgrade to asupported browser." Core functionality in gmail works fine, but I'm not sure of security ramifications of running an old browser, particularly when google advises against it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1664147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708311] Re: Manually added startup application is deleted
Thanks for the feedback Reuben. Closing now. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708311 Title: Manually added startup application is deleted Status in chromium-browser package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-session Since chromium-browser doesn't support X sessions, I tried adding a custom entry to Startup Applications. This works fine, but the .desktop file is regularly deleted. I am wondering if this happens whenever chromium is updated, because this happens once a day (I get it from the nightly build PPA). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-session-bin 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 Architecture: i386 Date: Wed Jan 26 21:12:46 2011 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708311] Re: Manually added startup application is deleted
It seems not. I think this bug can be closed, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708311 Title: Manually added startup application is deleted Status in chromium-browser package in Ubuntu: New Bug description: Binary package hint: gnome-session Since chromium-browser doesn't support X sessions, I tried adding a custom entry to Startup Applications. This works fine, but the .desktop file is regularly deleted. I am wondering if this happens whenever chromium is updated, because this happens once a day (I get it from the nightly build PPA). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-session-bin 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 Architecture: i386 Date: Wed Jan 26 21:12:46 2011 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 539246] Re: chromium renders as a dialog under UNE
UNE is not a thing any longer, AFAICT. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/539246 Title: chromium renders as a dialog under UNE Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Binary package hint: chromium-browser When using chromium-browser under UNE, the windows generated by default appear as a type of dialog box, and do not properly tile like other application windows do. Changing the theme and style had no effect on this bug. This may be an issue with maximus over chromium however, although chromium does do some funny window manipulation to hide the window decorations from the host system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/539246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 582922] Re: No support for window.home()
>From https://developer.mozilla.org/en-US/docs/Web/API/Window/home : « This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it. » ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/582922 Title: No support for window.home() Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Binary package hint: chromium-browser window.home() is a Javascript function to switch the current tab to the user's homepage. window.home() does not work in chromium, though it does work in FF and probably others. I've filed an upstream bug with a webkit/chromium patch. This is a tracking bug. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/582922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708704] Re: Notifications inconsistent with other Ubuntu notifications
So can this be patched in the Ubuntu packaged build to override that flag default? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708704 Title: Notifications inconsistent with other Ubuntu notifications Status in chromium-browser package in Ubuntu: Confirmed Bug description: Binary package hint: chromium-browser Today gmail/chromium told me I can get desktop notifications on new emails, which is a great feature. Unfortunately the notifications don't use the Ubuntu notifications APIs (libnotify?) and seem out of place. There was apparently some discussion on the Ayatana mailing list, but there didn't seem to be a conclusion. I think chromium on Ubuntu should use the existing infrastructure even if that results in some loss of features (HTML and interactivity) compared to other platforms. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 8.0.552.237~r70801-0ubuntu1~ucd~stable2~maverick ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 CrashDB: ubuntu Date: Thu Jan 27 17:43:02 2011 Desktop-Session: DESKTOP_SESSION = gnome GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685141] Re: System freezes after locking screen
I switched from the open source xserver-xorg-video-nouveau driver to nvidia-375 in the Additional Drivers tab of the Software & Updates application and was able to recover after locking my screen with Ctrl- Alt-L, which was locking up my mouse and keyboard before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1685141 Title: System freezes after locking screen Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: When locking the screen or whenever the screensaver starts automatically, I cannot log in again, but my system completely freezes and I have to restart the computer. In most cases I was able to do the restart by pressing Alt-REISUB, in some cases however I had to do a hard reset. This is a new bug in zesty (Ubuntu 17.04). In the previous version everything worked fine. I tested both the upgrade and a fresh new installation on the same computer. Package is gnome-screensaver version 3.6.1-7ubuntu5. I attach an excerpt from my syslog. Hope this might help to find the bug. I installed zesty on another computer (laptop) as well and there the bug did not appear. So I assume it has something to do with the installed graphics card or graphics driver. Installed graphics card in this case is: NVIDIA Corporation GF108 [GeForce GT 630] (rev a1). Update: After a few days the bug now appears on the second computer as well. However, I could unlock the screen and continue working, until suddenly (an hour later or so) the whole system froze. I add the kernel-nullpointer-dereference syslog of this event (syslog2.txt) to the attachments for this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1685141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 972720] Re: chromium crashes on startup with SIGSEGV
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/972720 Title: chromium crashes on startup with SIGSEGV Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Just after the latest update for Oneiric. Upstream report at http://code.google.com/p/chromium/issues/detail?id=121719 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/972720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1070833] Re: Chromium-Browser crashed with SIGSEGV in operator new
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1070833 Title: Chromium-Browser crashed with SIGSEGV in operator new Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Chromium-Browser crashed with SIGSEGV in operator new ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 22.0.1229.94~r161065-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 ChromiumPrefs: can't open profile /root/.config/chromium/Default/Preferences Date: Wed Oct 24 18:34:30 2012 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 226G 82G 133G 39% /\nudev devtmpfs 2.0G 4.0K 2.0G 1% /dev\ntmpfs tmpfs 793M 1.1M 792M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 2.0G 720K 2.0G 1% /run/shm\nnone tmpfs 100M 40K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 15M 380K 14M3% /\nudev 206K 548 205K1% /dev\ntmpfs 210K 478 209K1% /run\nnone 210K 4 210K1% /run/lock\nnone 210K 7 210K1% /run/shm\nnone 210K24 210K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to quantal on 2012-09-18 (36 days ago) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1070833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1419768] Re: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1419768 Title: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger() Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Reboot and crash. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: chromium-browser 40.0.2214.94-0ubuntu1.1120 Uname: Linux 3.19.0-031900rc7-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 9 09:50:42 2015 ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2014-09-25 (137 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=3854.13.1795024813\ --disable-breakpad\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,2,12,16,39\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0116\ --gpu-driver-vendor=Mesa\ --gpu-driver-version=10.4 Signal: 6 SourcePackage: chromium-browser StacktraceTop: base::debug::BreakDebugger() () from /usr/lib/chromium-browser/libs/libbase.so logging::LogMessage::~LogMessage() () from /usr/lib/chromium-browser/libs/libbase.so ui::X11EventSource::X11EventSource(_XDisplay*) () from /usr/lib/chromium-browser/libs/libx11_events_platform.so ui::PlatformEventSource::CreateDefault() () from /usr/lib/chromium-browser/libs/libx11_events_platform.so ?? () from /usr/lib/chromium-browser/libs/libcontent.so Title: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-25T10:51:09.836610 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1419768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 875712] Re: broken dependency (wrong version)
** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/875712 Title: broken dependency (wrong version) Status in chromium-browser package in Ubuntu: Invalid Bug description: Depends on cromium-browser 14.0.835.202~r103287-0ubuntu1 which is unavailable in repository. Available version is 13.0.782.215~r97094-0ubuntu2 instead. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser-l10n (not installed) Uname: Linux 2.6.38-1000-ac100 armv7l ApportVersion: 1.23-0ubuntu3 Architecture: armel Date: Sun Oct 16 21:05:56 2011 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/875712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 601969] Re: ERROR:gkr-operation.c:383:gkr_operation_block: assertion failed: (op->pending != pending)
** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/601969 Title: ERROR:gkr-operation.c:383:gkr_operation_block: assertion failed: (op->pending != pending) Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Fix Released Bug description: Binary package hint: chromium-browser chromium-browser crashes most the time if the new option --pasword-store=gnome / --pasword-store=detect is enabled. Here is my actual launcher: [CODE] /usr/lib/chromium-browser/chromium-browser --password-store=gnome --enable-sync-passwords --sync-url=https://clients4.google.com/chrome-sync/dev --new-wrench-menu [CODE] And here is the terminal output: [CODE] /usr/lib/chromium-browser/chromium-browser --password-store=gnome --enable-sync-passwords --sync-url=https://clients4.google.com/chrome-sync/dev --new-wrench-menu ERROR:gkr-operation.c:383:gkr_operation_block: assertion failed: (op->pending != pending) Aborted [9742:9742:2081376609:ERROR:chrome/app/chrome_dll_main.cc(248)] GLib-GObject: g_object_ref: assertion `object->ref_count > 0' failed [CODE] uname -a: Linux hummer 2.6.35-6-generic #9-Ubuntu SMP Sun Jul 4 23:19:16 UTC 2010 i686 GNU/Linux lsb_release -rd: Ubuntu 10.04 LTS chromium-browser: 6.0.457.0~svn20100705r51623-0ubuntu1~ucd1~lucid To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/601969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003978] Re: chromium-browser crashed with SIGSEGV in g_main_context_dispatch()
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1003978 Title: chromium-browser crashed with SIGSEGV in g_main_context_dispatch() Status in chromium-browser package in Ubuntu: Won't Fix Bug description: SegvAnalysis: Segfault happened at: 0x7f30c95d81fa: movw $0x0,0x6(%r12) PC (0x7f30c95d81fa) ok source "$0x0" ok destination "0x6(%r12)" (0x0006) not located in a known VMA region (need writable region!) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu May 24 16:44:00 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1003978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1002325] Re: SIGILL: chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1002325 Title: SIGILL: chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. $ chromium-browser --temp-profile # just to rule out custom configuration 2. Go to youtube.com/html5, opt in to html5 3. Go to http://www.youtube.com/watch_popup?v=-JryxdydOj0&vq=480 What happens: The tab goes Aw, Snap! and dmesg says "chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser". What I expect to happen: I haven't bothered to check how it should behave, but at least it shouldn't crash. Additional information: Seems to happen with both chromium-codecs-ffmpeg and chromium-codecs-ffmpeg-extra (from Medibuntu) alike. I'm attaching a backtrace. I did my best with it, but I'll readily admit I have no idea of its value. Please do advise me if I more -dbg packages or something else is needed. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1 Uname: Linux 3.3.3-030303-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 09ae689090491ca53449589269e4bfd8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 ChromiumPrefs: can't open profile /home/jani/.config/chromium/Default/Preferences Date: Mon May 21 17:30:49 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2011-11-21 (182 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1002325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1104654] Re: Chromium browser crashed with SIGSEGV
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1104654 Title: Chromium browser crashed with SIGSEGV Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Chromium browser crashed with SIGSEGV Logs: ProblemType: Crash Architecture: i386 Date: Fri Jan 25 07:45:38 2013 DistroRelease: Ubuntu 12.10 ExecutablePath: /usr/lib/chromium-browser/chromium-browser ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: chromium-browser 23.0.1271.97-0ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Fri Jan 25 07:47:18 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 226G 96G 119G 45% /\nudev devtmpfs 2.0G 4.0K 2.0G 1% /dev\ntmpfs tmpfs 793M 1.2M 792M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 2.0G 156K 2.0G 1% /run/shm\nnone tmpfs 100M 68K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 15M 489K 14M4% /\nudev 206K 526 205K1% /dev\ntmpfs 210K 454 209K1% /run\nnone 210K 4 210K1% /run/lock\nnone 210K 7 210K1% /run/shm\nnone 210K30 210K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1104654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 864158] Re: Chromium takes 3-5 seconds to close, open tabs
Closing due to the last update to this bug being almost 6 years old. Please file a new bug if this still applies to recent releases of chromium-browser. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/864158 Title: Chromium takes 3-5 seconds to close, open tabs Status in chromium-browser package in Ubuntu: Won't Fix Bug description: PROBLEM The version of Chromium included in the Oneiric Beta hangs for several seconds each time I close or open a tab. The problem is exacerbated by having multiple tabs open already, but is far worse than it was under Natty. HOW TO REPRODUCE 1. Open and close tabs in Chromium. 2. If step 1 does not reproduce the bug, open a half-dozen tabs first. More or fewer may be required depending on your system's specifications. 3. Compare performance seen in step 1 and step 2 to your experience using Chromium under Natty. EXPECTED BEHAVIOR I will not encounter significant performance regressions in essential apps upon upgrading to the new version. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 13.0.782.215~r97094-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Sat Oct 1 12:30:16 2011 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/864158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1250174] Re: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang()
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1250174 Title: chromium-browser crashed with SIGSEGV in content::GpuWatchdogThread::DeliberatelyTerminateToRecoverFromHang() Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Won't Fix Status in libdrm-2.4.23 package in Ubuntu: Confirmed Bug description: I was using Google Maps and Chromium froze up and crashed. After this, rendering of the new Google Maps page causes jagged lines to appear in the browser page display section, until I reboot the computer. Killing and relaunching Chromium doesn't fix the problem. The jagged lines still appear after computer reboot if I visit Google Maps again, and again won't disappear until I restart the computer. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: chromium-browser 30.0.1599.114-0ubuntu0.12.04.3 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ChromiumPrefs: can't open profile /home/jamesmaz/.config/chromium/Default/Preferences Date: Mon Nov 11 13:10:09 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ --channel=4656.10.459810737\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=0,6,18\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0106\ --gpu-driver-vendor=Mesa\ --gpu-driver-version=9.1.7 ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f82c62ad43e:movl $0x1337,0x0 PC (0x7f82c62ad43e) ok source "$0x1337" ok destination "0x0" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () from /usr/lib/chromium-browser/libs/libcontent.so base::MessageLoop::RunTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from /usr/lib/chromium-browser/libs/libbase.so ?? () from /usr/lib/chromium-browser/libs/libbase.so Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo chromium-default: CHROMIUM_FLAGS="" . /usr/lib/pepflashplugin-installer/pepflashplayer.sh mtime.conffile..etc.chromium.browser.default: 2013-11-10T15:09:15.272458 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1250174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1368217] Re: chromium-browser crashed with SIGSEGV
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1368217 Title: chromium-browser crashed with SIGSEGV Status in chromium-browser package in Ubuntu: Won't Fix Bug description: start chromium and crashed ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 11 15:42:53 2014 ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2014-06-26 (77 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=16963.0.1807323150\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,15,22\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x1002\ --gpu-device-id=0x6840\ --gpu-driver-vendor\ --gpu-driver-versi Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 Title: chromium-browser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo www-data modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1368217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1380212] Re: chromium-browser crashed with SIGSEGV
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1380212 Title: chromium-browser crashed with SIGSEGV Status in chromium-browser package in Ubuntu: Won't Fix Bug description: chromium crashed out while gracelessly shutting down. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 12 00:12:37 2014 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2014-06-14 (119 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=3200.0.945800868\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,15,22\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x1002\ --gpu-device-id=0x9830\ --gpu-driver-vendor\ --gpu-driver-versi SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: chromium-browser crashed with SIGSEGV UpgradeStatus: Upgraded to utopic on 2014-09-22 (19 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1380212/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1428601] Re: chromium-browser crashed with SIGSEGV in ui::()
Closing now as this report wasn’t investigated timely and is now too old to be meaningful. Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1428601 Title: chromium-browser crashed with SIGSEGV in ui::() Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Close windows of Chromium and Crash. :S ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: chromium-browser 40.0.2214.111-0ubuntu1.1121 Uname: Linux 4.0.0-04rc2-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 5 08:21:33 2015 ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2014-09-25 (161 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: chromium-browser\ --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ --ppapi-flash-version=15.0.0.152\ --enable-pinch SegvAnalysis: Segfault happened at: 0x7f4d0724be00:mov(%rsi),%rax PC (0x7f4d0724be00) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () from /usr/lib/chromium-browser/libs/libcompositor.so ui::LayerAnimationElement::Start(ui::LayerAnimationDelegate*, int) () from /usr/lib/chromium-browser/libs/libcompositor.so ui::LayerAnimator::StartSequenceImmediately(ui::LayerAnimationSequence*) () from /usr/lib/chromium-browser/libs/libcompositor.so ui::LayerAnimator::ProcessQueue() () from /usr/lib/chromium-browser/libs/libcompositor.so ui::LayerAnimator::FinishAnimation(ui::LayerAnimationSequence*, bool) () from /usr/lib/chromium-browser/libs/libcompositor.so Title: chromium-browser crashed with SIGSEGV in ui::LayerAnimationElement::Start() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-09-25T10:51:09.836610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1428601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686456] Re: Font size in tab titles too big compared to Windows since material design
** Attachment added: "windows-ubuntu-comparison_guides_zoomed-in.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1686456/+attachment/4868290/+files/windows-ubuntu-comparison_guides_zoomed-in.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1686456 Title: Font size in tab titles too big compared to Windows since material design Status in chromium-browser package in Ubuntu: New Bug description: Since Chromium's material design "update", font size in the tab titles is too large on Ubuntu 14.04 with Unity. It is way larger than it was on Ubuntu before the material design update, and still considerably larger than a current Chrome version on Windows 7, so this should probably be considered a bug. It makes less of the tab title visible compared to current Chrome on Windows 7 (and compared to old Chromium on Ubuntu) and as such less useful. See attachments for a comparison between Chrome 58.0.3029.81 on Windows 7 and Ubuntu's Chromium 58.0.3029.81-0ubuntu0.14.04.1172. On the screenshot in Windows 7, the title text "New Tab" is 47 px wide and 9 px tall. In Ubuntu, the same text is 58 px wide and 12 px tall. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1686456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686456] [NEW] Font size in tab titles too big compared to Windows since material design
Public bug reported: Since Chromium's material design "update", font size in the tab titles is too large on Ubuntu 14.04 with Unity. It is way larger than it was on Ubuntu before the material design update, and still considerably larger than a current Chrome version on Windows 7, so this should probably be considered a bug. It makes less of the tab title visible compared to current Chrome on Windows 7 (and compared to old Chromium on Ubuntu) and as such less useful. See attachments for a comparison between Chrome 58.0.3029.81 on Windows 7 and Ubuntu's Chromium 58.0.3029.81-0ubuntu0.14.04.1172. On the screenshot in Windows 7, the title text "New Tab" is 47 px wide and 9 px tall. In Ubuntu, the same text is 58 px wide and 12 px tall. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "windows-ubuntu-comparison.png" https://bugs.launchpad.net/bugs/1686456/+attachment/4868289/+files/windows-ubuntu-comparison.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1686456 Title: Font size in tab titles too big compared to Windows since material design Status in chromium-browser package in Ubuntu: New Bug description: Since Chromium's material design "update", font size in the tab titles is too large on Ubuntu 14.04 with Unity. It is way larger than it was on Ubuntu before the material design update, and still considerably larger than a current Chrome version on Windows 7, so this should probably be considered a bug. It makes less of the tab title visible compared to current Chrome on Windows 7 (and compared to old Chromium on Ubuntu) and as such less useful. See attachments for a comparison between Chrome 58.0.3029.81 on Windows 7 and Ubuntu's Chromium 58.0.3029.81-0ubuntu0.14.04.1172. On the screenshot in Windows 7, the title text "New Tab" is 47 px wide and 9 px tall. In Ubuntu, the same text is 58 px wide and 12 px tall. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1686456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708704] Re: Notifications inconsistent with other Ubuntu notifications
Indeed, I’m running chromium 59.0.3071.15 and was able to enable native desktop notifications (chrome://flags/#enable-native-notifications). ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708704 Title: Notifications inconsistent with other Ubuntu notifications Status in chromium-browser package in Ubuntu: Confirmed Bug description: Binary package hint: chromium-browser Today gmail/chromium told me I can get desktop notifications on new emails, which is a great feature. Unfortunately the notifications don't use the Ubuntu notifications APIs (libnotify?) and seem out of place. There was apparently some discussion on the Ayatana mailing list, but there didn't seem to be a conclusion. I think chromium on Ubuntu should use the existing infrastructure even if that results in some loss of features (HTML and interactivity) compared to other platforms. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 8.0.552.237~r70801-0ubuntu1~ucd~stable2~maverick ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 CrashDB: ubuntu Date: Thu Jan 27 17:43:02 2011 Desktop-Session: DESKTOP_SESSION = gnome GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 828840] Re: Fonts are being rendered improperly
Installing fonts-teluguvijayam results in chromium-browser rendering
correctly (or so it seems to my untrained eye) koodali.org.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/828840
Title:
Fonts are being rendered improperly
Status in Chromium Browser:
Unknown
Status in chromium-browser package in Ubuntu:
Invalid
Bug description:
Telugu fonts are not being rendered properly or there is not setting to set
the preferred font for a language. or its simply no support for Unicode in
chromium browser
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC270 Analog [ALC270 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gpvprasad 1850 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:10ec0270,103c1425,00100100
HDA:80862804,80860101,0010'
Controls : 19
Simple ctrls : 10
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=2a472ca7-f443-4a6d-b0d6-301ac68e6ac7
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Hewlett-Packard Presario CQ42 Notebook PC
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en
PATH=(custom, no user)
LANG=te_IN.UTF-8
LC_MESSAGES=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic
root=UUID=f77dc777-74ae-4d3a-9b93-845e69788afe ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-10-generic N/A
linux-backports-modules-2.6.38-10-generic N/A
linux-firmware 1.52
Tags: natty running-unity
Uname: Linux 2.6.38-10-generic i686
UpgradeStatus: Upgraded to natty on 2011-04-29 (110 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/20/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1425
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 54.26
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.16:bd05/20/2010:svnHewlett-Packard:pnPresarioCQ42NotebookPC:pvr049F110028100:rvnHewlett-Packard:rn1425:rvr54.26:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Presario CQ42 Notebook PC
dmi.product.version: 049F110028100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/828840/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 729563] Re: Does not register itself as a handler for http URIs
According to upstream bug report, this is fixed. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/729563 Title: Does not register itself as a handler for http URIs Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Fix Released Bug description: Binary package hint: chromium-browser When I set chromium-browser to be my default browser, URLs opened from other applications and xdg-open still open in Firefox. The exception is that Thunderbird will correctly open the URLs in chromium-browser. I originally submitted this as bug 726504 https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/726504 which was marked invalid with the comment "This isn't a bug in xdg-utils, chrome must register itself as a handler for http URIs." So as the same issue shows up with chromium-browser, which is from the repos (and to which I subsequently switched anyway because google-chrome- unstable was being unstable ;-) ), I'm reporting it again as a chromium-browser bug, that probably needs to be pushed upstream to google as Chrome itself exhibits the same issue - or at least similar, see below about the alternatives symlink. Chromium certainly *thinks* it's the default browser, and claims as such in its preferences dialogue. However: rachel@mab:~$ ls -l /etc/alternatives/x-www-browser lrwxrwxrwx 1 root root 22 2011-02-20 18:37 /etc/alternatives/x-www-browser -> /usr/bin/google-chrome That's not chromium-browser's binary, but Google Chrome's (specifically google-chrome-unstable in this case) so *that* changed this symlink but chromium-browser, set as default since, didn't. But Thunderbird *still* correctly opens its urls in chromium-browser and everything else still opens their urls in firefox. So I don't know what's going on there. Sorry I don't still have a Maverick machine around, so I can't confirm, but my memory is that I didn't have this problem on Maverick. But basically what it looks like is that the comment on the xdg-utils bug implies that there is a set mechanism for "registering" as a default browser that google chrome and chromium aren't using. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 9.0.597.107~r75357-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Mar 5 10:22:25 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to natty on 2011-02-26 (6 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/729563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 793836] Re: Chromium occasionally renders unclosable blank ghost windows from pop-up menus
Closing due to the last update to this bug being 5 years old. Please file a new bug if this still applies to recent releases of chromium- browser. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/793836 Title: Chromium occasionally renders unclosable blank ghost windows from pop- up menus Status in chromium-browser package in Ubuntu: Won't Fix Status in openbox package in Ubuntu: Invalid Bug description: Binary package hint: openbox On a Lubuntu Natty amd64 system in a Lubuntu Desktop session with openbox 3.4.11.2-0ubuntu3, chromium-browser 11.0.696.71~r86024-0ubuntu0.11.04.1, and libgtk2.0-0 2.24.4-0ubuntu2, unclosable, blank (light gray), borderless ghost windows sometimes appear. These appear to be windows and not just areas where the background or foreground elements are not being drawn, as clicking or using the scroll wheel while the mouse pointer is a ghost window has no effect (in particular, it does not have the effect of clicking or scrolling in the window behind it). However, the ghost windows cannot be switched to--clicking them does not change what window is in the foreground. These ghost windows appear in front of regular windows, but behind menus, which makes sense, if they are left over from menus (as menus can typically be displayed in front of all windows, including other menus). This seems most often to be triggered by closing a contextual menu (or sometimes an application menu). I think that every time it has happened, Google Chromium was running, and at least the first ghost window was "left behind" by a contextual menu in Chromium. I am not sure if any other applications trigger this. Closing Chromium makes the ghost windows go away, and they do not reappear when Chromium is restarted. Perhaps this bug is specific to chromium-browser, or perhaps something is going wrong in openbox as well. As detailed below, the ghost windows are not shown when openbox is not running. My system has the default Lubuntu configuration, so openbox is run automatically in a Lubuntu Desktop session with the command line "openbox --config-file /home/ek/.config/openbox/lubuntu-rc.xml". (I've attached the file lubuntu-rc.xml.) I ran "openbox --config-file /home/ek/.config/openbox/lubuntu-rc.xml --replace", but that did not make the ghost windows go away. Quitting the new openbox process with Ctrl+C (SIGINT) made the ghost windows go away, but they returned when I restarted openbox with that same command. I quit the replacement openbox instance again, and found that the original instance of openbox was still running. I tried unsuccessfully to kill it with SIGTERM; then I successfully killed it with SIGKILL. As expected, this did not change the behavior of the windows on my desktop. Restarting openbox once again restored the ghost windows, as expected. I've attached three screenshots. The first shows a normal desktop, with the ghost windows. The second shows an application (VLC) in full screen mode, with the ghost windows, and with a contextual menu in front of part of one of them. The third shows a desktop without the ghost windows, achieved by running openbox with the --replace flag as described above, then quitting the new instance with SIGINT. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: openbox 3.4.11.2-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic x86_64 Architecture: amd64 Date: Mon Jun 6 21:45:54 2011 ExecutablePath: /usr/bin/openbox InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413.1) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/793836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 779946] Re: chromium-browser cannot be executed from root account
** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/779946 Title: chromium-browser cannot be executed from root account Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Binary package hint: chromium-browser the policy of blocking root account to execute software is exactly the opposite of the concept of the root user. the root user, aka administrator, could do everything on the system, of course it will respond of the consequences. Therefore, please add some flag to chromium to leave the administrators browsing the web. Regards, Vincenzo ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: yelp 3.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Mon May 9 16:11:35 2011 ExecutablePath: /usr/bin/yelp InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yelp UpgradeStatus: Upgraded to natty on 2011-04-09 (30 days ago) XsessionErrors: (npviewer.bin:21057): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/immodules/im-ibus.so: wrong ELF class: ELFCLASS64 (npviewer.bin:21057): Gtk-WARNING **: Loading IM context type 'ibus' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/779946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 735722] Re: Text selection in Chromium is difficult and inconsistent with the rest of the desktop
This appears to be fixed in recent releases of chromium-browser. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/735722 Title: Text selection in Chromium is difficult and inconsistent with the rest of the desktop Status in Chromium Browser: Unknown Status in Unity: Invalid Status in chromium-browser package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser PROBLEM When clicking-and-dragging to highlight text (and/or onscreen elements) in Chromium, moving the mouse cursor to the left or right of the selectable area causes a gigantic swath of text and onscreen elements to be selected. I am not sure what determines how much is selected, but this behavior is most easily observable when working with text boxes. Other Ubuntu / Unity apps have text selection stop at the edge of a selectable text area, and require you to move the cursor up and down (while inside or outside the area) to expand the highlighted selection. This behavior is a usability concern because it breaks people's expectations and causes undesirable behavior, and an accessibility concern because it requires precise cursor positioning in order to highlight a passage that runs to the edge of a selectable area. HOW TO REPRODUCE 1. View this webpage in Chromium. 2. Highlight this text by clicking-and-dragging, and watch what happens when the mouse cursor is moved far enough to the left or the right. EXPECTED BEHAVIOR Chromium's text selection behavior will be identical to the rest of the Unity desktop's, and will not cause accessibility problems for people who have trouble using a pointing device precisely. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 10.0.648.133~r77742-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7 Uname: Linux 2.6.38-6-generic i686 Architecture: i386 Date: Tue Mar 15 16:33:41 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to natty on 2011-03-13 (1 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/735722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 747792] Re: chromium browser closes when minimize button is pressed
Closing due to the last update to this bug being almost 6 years old. Please file a new bug if this still applies to recent releases of chromium-browser. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/747792 Title: chromium browser closes when minimize button is pressed Status in chromium-browser package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser let me know if you need more info. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 10.0.648.204~r79063-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Apr 1 17:06:49 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/747792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 804799] Re: creating new tab = switched window focus
** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/804799 Title: creating new tab = switched window focus Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Fix Released Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/728267 but I do not have issues with middle clicking. In fact middle clicking should be the same (I assume) as right clicking a link then selecting "Open link in new tab", doing this works as expected for me. The best way for me to describe this issue is by simply showing you: http://www.youtube.com/watch?v=mitfmSI393E When I click the + sign on the tab bar to open a new tab while viewing a page other than the new tab page the window loses focus giving focus to another window open on my system. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 14.0.808.0~svn20110701r91253-0ubuntu1~ucd1~natty ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 ChromiumPrefs: browser/check_default_browser = **unset** (no such key yet) extensions/settings = (no entry found in the Preferences file) CrashDB: ubuntu Date: Sat Jul 2 12:36:11 2011 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/804799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 824010] Re: Chromium creates a new keyring every new start
Closing due to the last update to this bug being almost 6 years old. Please file a new bug if this still applies to recent releases of chromium-browser. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/824010 Title: Chromium creates a new keyring every new start Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Won't Fix Bug description: For some reason, chromium-browser started creating a new keyring every time I reboot and start it anew. [user@somewhere ~]$ cd .gnome2/keyrings/ [user@somewhere keyrings]$ ls cloudsn.keyring default_14.keyring default_6.keyring login_2.keyring default default_1.keyring default_7.keyring login_3.keyring default_10.keyring default_2.keyring default_8.keyring login.keyring default_11.keyring default_3.keyring default_9.keyring user.keystore default_12.keyring default_4.keyring default.keyring default_13.keyring default_5.keyring login_1.keyring ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 12.0.742.112~r90304-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed Aug 10 11:17:01 2011 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to natty on 2011-04-30 (102 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/824010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685272] Re: gnome-shell: no window border
The bug as described is not a theme issue, AFAICS. The window borders are meant to look like that. Are you really complaining about the lack of shadows? That *is* a bug. As far as I can see that particular issue only happens for csd windows. For example, gnome-terminal looks fine. ** Changed in: ubuntu-themes (Ubuntu Artful) Status: Confirmed => Triaged ** Changed in: ubuntu-themes (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685272 Title: gnome-shell: no window border Status in light-themes package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Triaged Status in light-themes source package in Artful: Invalid Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell, there are no window borders. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685271] Re: gnome-shell: corners are not rounded
Also for csd windows only ** Changed in: ubuntu-themes (Ubuntu Artful) Status: Confirmed => Triaged ** Changed in: ubuntu-themes (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685271 Title: gnome-shell: corners are not rounded Status in light-themes package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Triaged Status in light-themes source package in Artful: Invalid Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell apps have dark black squared top corners when they should be rounded. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 827316] Re: DuckDuckGo should be added to the search engine ballot
** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/827316 Title: DuckDuckGo should be added to the search engine ballot Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the Chromium browser is started in Lubuntu for the first time, a query is made to choose the default search engine. The search engine duckduckgo.com is missing from the list of choices. Please add it. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 12.0.742.112~r90304-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 ChromiumPrefs: browser/check_default_browser = **unset** (no such key yet) extensions/settings = (no entry found in the Preferences file) Date: Tue Aug 16 15:23:44 2011 Desktop-Session: DESKTOP_SESSION = Lubuntu XDG_CONFIG_DIRS = /etc/xdg/lubuntu:/etc/xdg XDG_DATA_DIRS = /etc/xdg/lubuntu:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg DetectedPlugins: (no entry found in the Preferences file) Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/827316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708704] Re: Notifications inconsistent with other Ubuntu notifications
According to http://www.omgubuntu.co.uk/2017/04/google-chrome-dev-lets- enable-native-desktop-notifications this is changing in chrome dev channel via an opt in flag. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708704 Title: Notifications inconsistent with other Ubuntu notifications Status in chromium-browser package in Ubuntu: Confirmed Bug description: Binary package hint: chromium-browser Today gmail/chromium told me I can get desktop notifications on new emails, which is a great feature. Unfortunately the notifications don't use the Ubuntu notifications APIs (libnotify?) and seem out of place. There was apparently some discussion on the Ayatana mailing list, but there didn't seem to be a conclusion. I think chromium on Ubuntu should use the existing infrastructure even if that results in some loss of features (HTML and interactivity) compared to other platforms. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 8.0.552.237~r70801-0ubuntu1~ucd~stable2~maverick ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 CrashDB: ubuntu Date: Thu Jan 27 17:43:02 2011 Desktop-Session: DESKTOP_SESSION = gnome GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 722171] Re: Some Launchpad links to source packages with epoch don't work in Chromium
*** This bug is a duplicate of bug 1629058 *** https://bugs.launchpad.net/bugs/1629058 ** This bug has been marked a duplicate of bug 1629058 DistributionSourcePackage:+index incorrectly links versions with epochs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/722171 Title: Some Launchpad links to source packages with epoch don't work in Chromium Status in chromium-browser package in Ubuntu: Confirmed Bug description: Binary package hint: chromium-browser Hi Some source package links from: https://launchpad.net/ubuntu/+source/git are working and others aren't The "Latest upload" link: 1:1.7.4.1-1 works, but the "Natty Narwhal" link to the latest version of the source package 1:1.7.4.1-1 doesn't: if I open it, the address bar shows: %31:1.7.4.1-1 Cheers, --- Architecture: amd64 Desktop-Session: DESKTOP_SESSION = gnome-classic XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-classic:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome-classic:/usr/share/gnome:/usr/local/share/:/usr/share/ DistroRelease: Ubuntu 11.04 Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None Package: chromium-browser 9.0.597.94~r73967-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=(custom, user) LANG=fr_FR.UTF-8 LC_MESSAGES=fr_FR.utf8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Tags: unity-2d natty Uname: Linux 2.6.38-4-generic x86_64 UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild chromium-default: CHROMIUM_FLAGS="-start-maximized" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/722171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 754580] Re: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible.
In recent releases of chromium-browser, dragging a tab out of a window instantly creates a new window, which cannot be dragged into a launcher icon indeed. But that looks intentional. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Won't Fix -- 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/754580 Title: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible. Status in Ayatana Design: Fix Committed Status in Chromium Browser: New Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in chromium-browser package in Ubuntu: Won't Fix Status in firefox package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [Impact] It's not possible to drag firefox or chromium tabs to the relative launcher icon in order to select a different window as drop target. [Test case] 1. Open two Chromium or Firefox windows, with two tabs open in each. 2. Start dragging a browser tab over a browser icon in the Launcher 3. Unity should displays a spread of the two browser windows 4. It will be possible to drop the tab in one of the browser windows, after selecting it in spread. [Regression Potential] As it happened with bug #727902 this codepath was disabled in the past, thus there's basically no regression potential. --- With Metacity, one would need only to drag the tab to the bottom bar, mouse-over the destination window, and then release the tab in the newly focused window. There is no equivalent behavior with Unity. Dragging tabs to its bar does nothing. - Desired resolution: Users should be able to move tabs between browser windows irrespective of window state (minimised, restored or maximised) by dragging and dropping the via the Launcher app spread. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/754580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686345] Re: apt-get libmagick++-6.q16-6v6 depend missing
Well, the problem is not of the package in ubuntu, which is correctly built against libmagick++-6.q16-7 instead of libmagick++-6.q16-6v6. Whoever maintains the PPA ppa:inkscape.dev/stable has to do another upload to rebuild inkscape there. Subscribing ~bryce who did the last upload there ** Changed in: inkscape (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1686345 Title: apt-get libmagick++-6.q16-6v6 depend missing Status in inkscape package in Ubuntu: Invalid Bug description: Ubuntu Gnome 17.04, apt update-ed When installing inkscape with apt install inkscape, the installation fails complaining on missing depends: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: inkscape : Depends: libmagick++-6.q16-6v6 (>= 8:6.9.2.3) but it is not installable Recommends: libwmf-bin Recommends: perlmagick Recommends: python-lxml but it is not going to be installed Recommends: python-numpy but it is not going to be installed Recommends: python-scour but it is not going to be installed Recommends: python-uniconvertor but it is not going to be installed E: Unable to correct problems, you have held broken packages. It seems that libmagick++-6.q16-6v6 was removed from 17.04 but inkscape package is not updated version info: inkscape: Installed: (none) Candidate: 0.92.1+66~ubuntu17.04.1 Version table: 0.92.1+66~ubuntu17.04.1 500 500 http://ppa.launchpad.net/inkscape.dev/stable/ubuntu zesty/main amd64 Packages 0.92.1-1 500 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1686345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685037] Re: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver
Where do you see that chromium-browser suggests chromedriver and firefoxdriver in xenial? $ apt show chromium-browser Package: chromium-browser Version: 58.0.3029.81-0ubuntu0.16.04.1277 […] Recommends: chromium-browser-l10n Suggests: webaccounts-chromium-extension, unity-chromium-extension, adobe-flashplugin […] ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1685037 Title: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver Status in chromium-browser package in Ubuntu: Incomplete Status in python-selenium package in Ubuntu: Confirmed Bug description: In Xenial this package suggests two other packgages: chromedriver and firefoxdriver. These packgages are not available in Xenial. Only Chromium-chromedriver is. Unfortunately, python-selenium does not provide webdrivers, so they have to be installed separately. Why aren’t they available? This greatly hampers the usefulness of python-selenium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1685037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 736033] Re: chromium doesn't respect command line options
chromium will respect the system-wide proxy settings (HTTP[S]_PROXY environment variable and friends). ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/736033 Title: chromium doesn't respect command line options Status in chromium-browser package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser Since chromium doesn't have any decent way to block flash or other crap, I installed privoxy. I then tried to run 'chromium --proxy- server=localhost:8118', but it still loaded everything, and nothing was reported in /var/log/privoxy/logfile. I then tried --proxy-server=butt.head.browser:666, but lo and behold, chromium still opened up, with no indication of anything wrong. There appears to be no way to view the proxy configuration from within chromium, but apparently, the command line options are just silently ignored. (Sorry if there's a load of crap accompanying this report, apparently, the "Report a bug" button has been redirected to a drool-proof page of how to report bugs, so I needed to randomly run apport to get to this web page. Look, Canonical, if you don't want bug reports, you can just say so.). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: upstart 0.6.6-4 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Wed Mar 16 11:25:10 2011 ExecutablePath: /sbin/init InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: PATH=(custom, no user) SourcePackage: upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/736033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 708704] Re: Notifications inconsistent with other Ubuntu notifications
Still valid. Desktop notifications do not use notify-osd. I'm not aware of any upstream plans to do that, though. ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/708704 Title: Notifications inconsistent with other Ubuntu notifications Status in chromium-browser package in Ubuntu: Confirmed Bug description: Binary package hint: chromium-browser Today gmail/chromium told me I can get desktop notifications on new emails, which is a great feature. Unfortunately the notifications don't use the Ubuntu notifications APIs (libnotify?) and seem out of place. There was apparently some discussion on the Ayatana mailing list, but there didn't seem to be a conclusion. I think chromium on Ubuntu should use the existing infrastructure even if that results in some loss of features (HTML and interactivity) compared to other platforms. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 8.0.552.237~r70801-0ubuntu1~ucd~stable2~maverick ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 CrashDB: ubuntu Date: Thu Jan 27 17:43:02 2011 Desktop-Session: DESKTOP_SESSION = gnome GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/708704/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 710127] Re: Desktop notifications from Chromium can not be closed
And according to the upstream bug report, this was a metacity bug. ** Changed in: chromium-browser (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/710127 Title: Desktop notifications from Chromium can not be closed Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser Desktop notifications from Chromium can only be closed in the first few seconds after appearing. After this time they remain open, hovering the 'x' for closing doesn't work and the only workaround is to disable and re-enable compositing (in my case: metacity compositing). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 8.0.552.237~r70801-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 NonfreeKernelModules: wl Architecture: i386 CheckboxSubmission: 60acb532cba35348c06d5739fe7dc5e8 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sun Jan 30 13:06:17 2011 Desktop-Session: DESKTOP_SESSION = gnome GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: SourcePackage: chromium-browser chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/710127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 710127] Re: Desktop notifications from Chromium can not be closed
Closing due to the last update to this bug being 6 years old. Please file a new bug if this still applies to recent releases of chromium- browser. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/710127 Title: Desktop notifications from Chromium can not be closed Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser Desktop notifications from Chromium can only be closed in the first few seconds after appearing. After this time they remain open, hovering the 'x' for closing doesn't work and the only workaround is to disable and re-enable compositing (in my case: metacity compositing). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 8.0.552.237~r70801-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 NonfreeKernelModules: wl Architecture: i386 CheckboxSubmission: 60acb532cba35348c06d5739fe7dc5e8 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sun Jan 30 13:06:17 2011 Desktop-Session: DESKTOP_SESSION = gnome GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: SourcePackage: chromium-browser chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/710127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 728267] Re: Opening new tabs while another Chromium window is full-screened switches focus to the full-screened window
Closing due to the last update to this bug being 6 years old. Please file a new bug if this still applies to recent releases of chromium- browser. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/728267 Title: Opening new tabs while another Chromium window is full-screened switches focus to the full-screened window Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Binary package hint: chromium-browser PROBLEM Opening new tabs by middle-clicking a link, while another Chromium window is full-screened, switches focus to the full-screened window for no apparent reason. HOW TO REPRODUCE 1. Open two separate Chromium windows. 2. Full-screen one of them. 3. Middle-click on a link in the Chromium window that is not full-screened, so as to open it. EXPECTED BEHAVIOR Having one Chromium window full-screened won't break normal behavior in other windows. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 9.0.597.94~r73967-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Thu Mar 3 01:54:28 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: chromium-browser chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/728267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 727062] Re: Browser tabs crash after some time display chrash message inside tab
Closing due to the last update to this bug being 6 years old. Please file a new bug if this still applies to recent releases of chromium- browser. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/727062 Title: Browser tabs crash after some time display chrash message inside tab Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Binary package hint: chromium-browser I am using chromium 10.0.648.114 (75702) Ubuntu 10.10 version. It crashes if try to open more tab and display the "Aw snap" message. Please refer screen shot for detail. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 10.0.648.114~r75702-0ubuntu1~ucd~beta1~maverick ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 NonfreeKernelModules: fglrx Architecture: i386 CrashDB: ubuntu Date: Tue Mar 1 15:15:51 2011 Desktop-Session: DESKTOP_SESSION = xsession XDG_CONFIG_DIRS = /etc/xdg/xdg-xsession:/etc/xdg XDG_DATA_DIRS = /usr/share/xsession:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100317.1) ProcEnviron: PATH=(custom, user) LANG=en_IN.utf8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/727062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 776170] Re: chromium makes sounds whenever I open or close tabs
Closing due to the last update to this bug being 4 years old. Please file a new bug if this still applies to recent releases of chromium- browser. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/776170 Title: chromium makes sounds whenever I open or close tabs Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Binary package hint: chromium-browser Something is causing the browser to play /usr/share/sounds/ubuntu/stereo/button-pressed.ogg every time I open or close a tab. Note that I'm running a KDE3 (Trinity) desktop and not gnome. Some googling suggests running gnome-volume-control, but that only results in a "Waiting for sound system to respond" dialog and repeated "** (gnome-volume-control:12718): WARNING **: Connection failed, reconnecting..." messages on the console. I understand this is because I don't have pulseaudio installed (as I don't have anything that actually uses it). Other suggestions include uninstalling the package that provides the offending sound file(s), but this strikes me as shooting the messenger, so to speak. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 10.0.648.205~r81283-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-generic x86_64 Architecture: amd64 Date: Tue May 3 14:37:14 2011 Desktop-Session: DESKTOP_SESSION = kde3 GNOME_DESKTOP_SESSION_ID = None XDG_CONFIG_DIRS = /etc/xdg/xdg-kde3:/etc/xdg:/opt/kde3/etc/xdg/:/etc/xdg/ XDG_DATA_DIRS = /usr/share/kde3:/usr/local/share/:/usr/share/:/opt/kde3/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: PATH=(custom, no user) LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: chromium-browser chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/776170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
