[Desktop-packages] [Bug 1968581] Re: Invalid transition after update to 1.18.6-1
Lenovo-shipped EM7455, 1199:9079 Adding the symlink didn't solve the problem. I found that the qmicli was not installed ! After installing libqmi-utils package I could solve the problem. Does the upgrade to ubuntu 22.04 uninstalled me the libqmi-utils package? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1968581 Title: Invalid transition after update to 1.18.6-1 Status in modemmanager package in Ubuntu: Incomplete Bug description: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1968581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968581] Re: Invalid transition after update to 1.18.6-1
There is a description of the problem here: https://modemmanager.org/docs/modemmanager/fcc-unlock/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1968581 Title: Invalid transition after update to 1.18.6-1 Status in modemmanager package in Ubuntu: New Bug description: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1968581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968581] [NEW] Invalid transition after update to 1.18.6-1
Public bug reported: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1968581 Title: Invalid transition after update to 1.18.6-1 Status in modemmanager package in Ubuntu: New Bug description: Unable to connect. Log information: [1649685973.4066] device (cdc-wdm2): Activation: starting connection 'Sunrise Default 1' (78490efe-5f5f-4b6f-a951-399fca325d19) NetworkManager[1004]: [1649685973.4071] audit: op="connection-activate" uuid="78490efe-5f5f-4b6f-a951-399fca325d19" name="Sunrise Default 1" pid=3375 uid=1000 result="success" NetworkManager[1004]: [1649685973.4075] device (cdc-wdm2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4094] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4122] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685973.4126] device (cdc-wdm2): state change: prepare -> need-auth (reason 'none', sys-iface-state: 'managed') NetworkManager[1004]: [1649685978.4260] device (cdc-wdm2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) NetworkManager[1004]: [1649685978.6019] device (cdc-wdm2): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed') ModemManager[9630]: [modem0] simple connect started... ModemManager[9630]: [modem0] simple connect state (3/8): enable ModemManager[9630]: [modem0] state changed (disabled -> enabling) ModemManager[9630]: [modem0] Failure ModemManager[9630]: [modem0] Failure AModemManager[9630]: [modem0] couldn't enable interface: 'Invalid transition' ModemManager[9630]: [modem0] state changed (enabling -> disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1968581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905373] [NEW] Xorg freeze when monitor turned off and on
Public bug reported: I have two monitors on a Radeon R9 380X, one is connected to HDMI, the other is connected to DVI. When I turn off the left monitor, nothing happens. Only when you turn it on again does the entire picture move to the right monitor and Ubuntu does not react to keyboard or mouse input. The problem only occurs once I've logged in. Even if I've locked the screen again. Hard reboot is required. == Ubuntu: Description:Ubuntu 20.04.1 LTS Release:20.04 xorg: Installiert: 1:7.7+19ubuntu14 Installationskandidat: 1:7.7+19ubuntu14 Versionstabelle: *** 1:7.7+19ubuntu14 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 09:44:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XT / Amethyst XT [Radeon R9 380X / R9 M295X] [1002:6938] (rev f1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380X Nitro 4G D5 [174b:e308] InstallationDate: Installed on 2019-09-15 (435 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7978 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=876f1728-1e76-4498-a415-504e1078f473 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.70 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd07/24/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu ** Attachment added: "problem looks like this" https://bugs.launchpad.net/bugs/1905373/+attachment/5437443/+files/cropped_monitors -- 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/1905373 Title: Xorg freeze when monitor turned off and on Status in xorg package in Ubuntu: New Bug description: I have two monitors on a Radeon R9 380X, one is connected to HDMI, the other is connected to DVI. When I turn off the left monitor, nothing happens. Only when you turn it on again does the entire picture move to the right monitor and Ubuntu does not react to keyboard or mouse input. The problem only occurs once I've logged in. Even if I've locked the screen again. Hard reboot is required. == Ubuntu: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installiert: 1:7.7+19ubuntu14 Installationskandidat: 1:7.7+19ubuntu14 Versionstabelle: *** 1:7.7+19ubuntu14 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5Che
[Desktop-packages] [Bug 1898324] Re: Different thickness title bars between gtk3 / gtk2 applications
Hi, gtk3 does not have titlebars, those are headerbar and I think we should not compare them. The relationship is more between gtk3 headerbars and gtk2 titlebars+menubar, so if we make titlebar as tall as headerbar we will just end up wasting space (considering that headerbar are already quite thick, maybe too much, in my opinion). ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1898324 Title: Different thickness title bars between gtk3 / gtk2 applications Status in yaru-theme package in Ubuntu: Opinion Bug description: I'm using Ubuntu 20.10 (beta). The title bar thickness is different between gtk3 / gtk2 applications. Gtk3 applications have a thicker title bar. I think all thickness must be the same to keep the visual identity of the OS. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 02:16:27 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1898324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph
You might know it already, but there is a gnome shell extension that, among many other tweaks, also adds a custom logo to the "activities" label. https://extensions.gnome.org/extension/358/activities-configurator/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1707831 Title: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Bug description: I suggest replacing the "Activities" label with the Ubuntu icon/logo. "Activities" sounds awkward and misleading. It would be more suitably vague, and more consistent with the existing Unity7 experience if the Gnome Shell "Activities" label was replaced by just the Ubuntu logo. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:28:08 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1707831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph
In the past we had the Ubuntu logo exactly as Red Hat has its own, but then we removed it for some problems related to the length of the "activity" label once translated. Basically we got different spacing according to the length of the text, and the logo looked misaligned or even overlapped the text in some cases. Some more context here https://discourse.ubuntu.com/t/call-for- participation-an-ubuntu-default-theme-lead-by-the-community/1545/1494 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1707831 Title: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Bug description: I suggest replacing the "Activities" label with the Ubuntu icon/logo. "Activities" sounds awkward and misleading. It would be more suitably vague, and more consistent with the existing Unity7 experience if the Gnome Shell "Activities" label was replaced by just the Ubuntu logo. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:28:08 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1707831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894909] Re: Feature Request: Ability to change "Applications Overview" button style.
Hi, this detail has been discussed a lot in the past on Yaru repo. The summary is that for the purpose of the icon, the grid seems to be the best representation so far. With this in mind we decided to keep the icon, but we are not closed to proposals. I leave here some links to go into the details of the discussions - [New app grid icon (yes, again)](https://github.com/ubuntu/yaru/issues/796) - [Use the app grid icon instead of the ubuntu logo](https://github.com/ubuntu/yaru/issues/584) ** Bug watch added: github.com/ubuntu/yaru/issues #796 https://github.com/ubuntu/yaru/issues/796 ** Bug watch added: github.com/ubuntu/yaru/issues #584 https://github.com/ubuntu/yaru/issues/584 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1894909 Title: Feature Request: Ability to change "Applications Overview" button style. Status in gnome-shell package in Ubuntu: Invalid Bug description: 1) Ubuntu 20.04 2) Gnome 3.36 3) There could be an option to change the "Applications Overview" button style. Currently, the "Applications Overview" button style is a 3x3 grid. There could be a 3x3 grid option, Ubuntu logo option, (any other suggested icons) and a custom icon option. 4) There is not an option to change the "Applications Overview" button style. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Nevermind my last comment. This works in chromium (no idea about snapd). To get this to work in chromium, first make sure it works for xdg-open. Click on the link that you want to be opened automatically in some application. When it downloaded, right-click on it (the button that appeared on the bottom) and select "Always open files of this type"; this will cause chromium to use xdg-open next time you open a file of that type. To make xdg-open work, run "xdg-mime query filetype the-downloaded-file", this should print the correct mime type. Then run "xdg-mime query default that-mime-type", this should print the desktop file that you want to use, aka "myapplication.desktop". Inside that .desktop then (.local/share/applications/the-file.desktop), there should be the lines Exec=/path/your/application and MimeType=that-mime-type Anyway, plenty of tutorial on xdg on the net. I missed the chromium trick to make it use xdg-open in the first place. -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
I am also affected by this horrible show stopper bug. Using Arch Linux and chromium browser. Seeing that this has been reported 8 months ago and the severity is set to "undecided" for chromium, it is clear that I'll have to start to use a different browser. This saddens me a lot :( -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878998] Re: Value in Yaru-dark/gnome-shell/gnome-shell.css not used
Hi Daniel, in gnome-shell selected text inside a StEntry is supposed to have orange background and white text, regardless the variant (light or dark), so I don't expect this issue to be related to bug 1842886, unless I am missing something here. We have the same issue reported in Yaru's github repo and I worked a little on it without being able to have a selected foreground color work yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878998 Title: Value in Yaru-dark/gnome-shell/gnome-shell.css not used Status in gnome-shell package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: The value for selected-color at line 153 in the gnome-shell.css files for Yaru and Yaru-dark is ignored by the shell. (Selected text should change color from dark grey to white.) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-17 (214 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: yaru-theme PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxsf _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878199] [NEW] Check and Radio buttons state is unclear in GTK2
Public bug reported: It seems that GTK2 uses the new black and white menu-check and menu- radio buttons instead the non-menu counterparts, resulting in a confused representation of their state. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Radio button in gtk2" https://bugs.launchpad.net/bugs/1878199/+attachment/5370313/+files/radio--button-gtk2.png ** Package changed: gnome-software (Ubuntu) => yaru-theme (Ubuntu) -- 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/1878199 Title: Check and Radio buttons state is unclear in GTK2 Status in yaru-theme package in Ubuntu: New Bug description: It seems that GTK2 uses the new black and white menu-check and menu- radio buttons instead the non-menu counterparts, resulting in a confused representation of their state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1878199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878198] [NEW] Ubuntu-Software icon should not be used for Gnome-Software
Public bug reported: org.gnome.Software and ubuntu software icons are very similar and causes confusion for users that choose to install gnome-software for flatpak support First reported here https://github.com/ubuntu/yaru/issues/2144#issuecomment-620092334 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Icons for Ubuntu Software and Gnome Software apps" https://bugs.launchpad.net/bugs/1878198/+attachment/5370311/+files/software-stores-icons.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1878198 Title: Ubuntu-Software icon should not be used for Gnome-Software Status in yaru-theme package in Ubuntu: New Bug description: org.gnome.Software and ubuntu software icons are very similar and causes confusion for users that choose to install gnome-software for flatpak support First reported here https://github.com/ubuntu/yaru/issues/2144#issuecomment-620092334 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1878198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877468] [NEW] GNOME dictionary uses symbolic icon
Public bug reported: Gnome dictionary installed from Ubuntu software, uses the dictionary's symbolic icon. It might use a proper fullcolor icon from Yaru set ** Affects: yaru-theme (Ubuntu) Importance: Undecided Assignee: Carlo Lobrano (c-lobrano) Status: New ** Attachment added: "gnome dictionary with the symbolic icon" https://bugs.launchpad.net/bugs/1877468/+attachment/5368067/+files/gnome-dict-symbolic.png ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Carlo Lobrano (c-lobrano) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1877468 Title: GNOME dictionary uses symbolic icon Status in yaru-theme package in Ubuntu: New Bug description: Gnome dictionary installed from Ubuntu software, uses the dictionary's symbolic icon. It might use a proper fullcolor icon from Yaru set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1877468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873394] Re: Terminal does not respond to theme changes
This is intended. Gnome-terminal is shipped with "prefer-dark" enabled, so it keeps the dark theme unless you change the application configuration clicking on options (the "hamburger" menu) > preferences > theme variant menu ** Changed in: yaru-theme (Ubuntu) Status: New => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1873394 Title: Terminal does not respond to theme changes Status in gnome-terminal package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Invalid Bug description: Terminal does not respond to theme changes. In the Settings app > Appearance > Window theme, I can select Light, Standard or Dark. Changing this setting seems to affect all other apps but not Terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1873394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871586] [NEW] Some updates require UI freeze exceptions
Public bug reported: Yaru version 20.04.4 needs some updates that require UI freeze exception. As suggested, I opened this ticket as container for speed up the review - LP #1869141 [UIFe] Icon View Captions labels in Nautilus are hard to read when selected - LP #1870925 UI freeze exception to remove problematic legacy action icons - GitHub: Adding symbols for system-reboot and system-log-out #2118 - GitHub: shell/switcher-popup: improve contrast of highlighted app #2138 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1871586 Title: Some updates require UI freeze exceptions Status in yaru-theme package in Ubuntu: New Bug description: Yaru version 20.04.4 needs some updates that require UI freeze exception. As suggested, I opened this ticket as container for speed up the review - LP #1869141 [UIFe] Icon View Captions labels in Nautilus are hard to read when selected - LP #1870925 UI freeze exception to remove problematic legacy action icons - GitHub: Adding symbols for system-reboot and system-log-out #2118 - GitHub: shell/switcher-popup: improve contrast of highlighted app #2138 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1871586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
As reported in the upstream ticket, the "Classic" gedit colorscheme does not fit well with dark theme, both Yaru and Adwaita, but there are others to choose. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Is the problem reproducible with adwaita-dark? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869141] [NEW] [UIFe] Icon View Captions labels in Nautilus are hard to read when selected
Public bug reported: First reported here: https://github.com/ubuntu/yaru/issues/2110 The "Icon View Captions" label in Nautilus is hard to read when the file is selected. Steps to Reproduce the Problem - open Preferences > View Tab - in the "Icon View Captions" section select at least one "information to be displayed beneath file and folders name" - Go back to Nautilus main window and select Icon View. Below the file name is expected to be a new label with color gray - Select the icon. The caption label keeps the gray color, which is hard to read on an orange background Yaru version - Version 20.04.4 in current Focal daily The fix has a low impact, since it only applies to Yaru's stylesheet part dedicated to Nautilus, and specifically to this caption labels. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Assignee: Carlo Lobrano (c-lobrano) Status: New ** Attachment added: "picture of the caption label when selected" https://bugs.launchpad.net/bugs/1869141/+attachment/5341770/+files/nautilus-caption-before.png ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Carlo Lobrano (c-lobrano) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1869141 Title: [UIFe] Icon View Captions labels in Nautilus are hard to read when selected Status in yaru-theme package in Ubuntu: New Bug description: First reported here: https://github.com/ubuntu/yaru/issues/2110 The "Icon View Captions" label in Nautilus is hard to read when the file is selected. Steps to Reproduce the Problem - open Preferences > View Tab - in the "Icon View Captions" section select at least one "information to be displayed beneath file and folders name" - Go back to Nautilus main window and select Icon View. Below the file name is expected to be a new label with color gray - Select the icon. The caption label keeps the gray color, which is hard to read on an orange background Yaru version - Version 20.04.4 in current Focal daily The fix has a low impact, since it only applies to Yaru's stylesheet part dedicated to Nautilus, and specifically to this caption labels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1869141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Hi Daniel, do you think that removing Yaru's style would have a positive impact on this issue or it would be useless? The slice of css you reported comes from a file containing specific style for applications that can be dropped easily if not necessary (and even more easily if harmful) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: New Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865871] [NEW] appearance setting view shows thick border
Public bug reported: Appearance setting seems to have a double border in the separation from the sidebar steps to reproduce 1. open gnome-control-center 2. click on appearance tab 3. compare the border-from-sidebar with another setting page lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu2 Candidate: 1:3.35.91-0ubuntu2 Version table: *** 1:3.35.91-0ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 13:28:14 2020 InstallationDate: Installed on 2020-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "appearance setting picture" https://bugs.launchpad.net/bugs/1865871/+attachment/5333031/+files/appearance-setting.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865871 Title: appearance setting view shows thick border Status in gnome-control-center package in Ubuntu: New Bug description: Appearance setting seems to have a double border in the separation from the sidebar steps to reproduce 1. open gnome-control-center 2. click on appearance tab 3. compare the border-from-sidebar with another setting page lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu2 Candidate: 1:3.35.91-0ubuntu2 Version table: *** 1:3.35.91-0ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 13:28:14 2020 InstallationDate: Installed on 2020-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1865871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: yaru-dark doesn't work well with highlighted current line in gedit
** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: yaru-dark doesn't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: New Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853774] Re: Keep track of upstream adwaita-icon-theme
It is not easy to implement this automatically, but we are already keeping an eye on adwaita icon theme ** Changed in: yaru-theme (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1853774 Title: Keep track of upstream adwaita-icon-theme Status in Yaru Theme: New Status in yaru-theme package in Ubuntu: Invalid Bug description: Since Yaru is now syncing with upstream adwaita-gtk and gnome-shell themes, I think it would be a good idea to also keep an eye on upstream adwaita-icon-theme. adwaita-icon-theme mostly contains symbolic and action icons that correspond to code changes in gnome-shell, gnome-control-center and the rest of gnome apps. In every gnome development cycle, adwaita-icon-theme adds, fixes, or enhances its symbolic icons in order to reflect the code changes in the gnome stack. adwaita-icon-theme does not contain app icons since gnome apps ship their own icons. An example to elaborate: In the 3.34 development cycle, gnome added new battery icons in order to better represent the battery charge states: https://gitlab.gnome.org/GNOME/adwaita-icon-theme/issues/6 That has resulted in: 21 new battery icons in adwaita-icon-theme and moving the legacy battery icons to a legacy folder: https://gitlab.gnome.org/GNOME/adwaita-icon-theme/commit/377044f755c3ec994f661d787f50e633487b929d Code changes in gnome-shell to use the new icons, if available, and fall back to the existing icon names for compatibility with older icon themes: https://gitlab.gnome.org/GNOME/gnome-shell/commit/bd18313d125aa1873c21b9cce9bbf81a335e48b0 Without reflecting the new changes in Yaru*, gnome-shell would still be falling back to the legacy icons, and not showing a better charge state as a result. * https://github.com/ubuntu/yaru/issues/1482 Here is the gnome-stencils.svg as a reference: https://gitlab.gnome.org/GNOME/adwaita-icon-theme/blob/master/src/symbolic/gnome-stencils.svg To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818968] Re: can't select text from the start of a line on a terminator shell
** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1818968 Title: can't select text from the start of a line on a terminator shell Status in Yaru Theme: New Status in yaru-theme package in Ubuntu: Invalid Bug description: Ever since yaru became the default theme, I'm not able to select text from the start of the line anymore, instead it'll try to resize the split terminator shell. To reproduce: - open terminator - split the window vertically - try to select text on the right side terminal - notice you can't select the first character, instead it will try to resize the split To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1818968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854661] Re: If an app is active, instead of displaying a red dot next to the dash icon, why not display a green dot?
** Changed in: yaru-theme (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1854661 Title: If an app is active, instead of displaying a red dot next to the dash icon, why not display a green dot? Status in Ubuntu UX: New Status in yaru-theme package in Ubuntu: Opinion Bug description: Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1854661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818968] Re: can't select text from the start of a line on a terminator shell
This bug has been discussed also here https://github.com/ubuntu/yaru/issues/1243 and resulted in an upstream ticket https://gitlab.gnome.org/GNOME/gtk/issues/1768 since > we don't have a custom handle and we use Adwaita's one here ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #1768 https://gitlab.gnome.org/GNOME/gtk/issues/1768 ** Also affects: yaru via https://gitlab.gnome.org/GNOME/gtk/issues/1768 Importance: Unknown Status: Unknown ** Bug watch added: github.com/ubuntu/yaru/issues #1243 https://github.com/ubuntu/yaru/issues/1243 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1818968 Title: can't select text from the start of a line on a terminator shell Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Confirmed Bug description: Ever since yaru became the default theme, I'm not able to select text from the start of the line anymore, instead it'll try to resize the split terminator shell. To reproduce: - open terminator - split the window vertically - try to select text on the right side terminal - notice you can't select the first character, instead it will try to resize the split To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1818968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799204] Re: yaru-dark has no gtk2 compatibility
Bug #1799217 has been solved and this one as well ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1799204 Title: yaru-dark has no gtk2 compatibility Status in yaru-theme package in Ubuntu: Fix Released Bug description: if you use yaru-dark, apps wich are using gtk 2 themes like transgui or gmpc will be shown in an old motif-like theme. There is no issue with regular yaru theme. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gtk 18.10.6 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 14:31:23 2018 InstallationDate: Installed on 2018-02-15 (249 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1799204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850260] Re: white color theme in yaru
Setting this as "invalid" since it is not a bug. Let me know if this is a mistake, thank ** Changed in: yaru-theme (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1850260 Title: white color theme in yaru Status in yaru-theme package in Ubuntu: Invalid Bug description: Hello! After update from 19.04 to 19.10 in Yaru theme part of dark scenery has become light coloured. Screenshot in attach. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1850260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809564] Re: Unfocused tilix window transparency
** Changed in: yaru-theme (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1809564 Title: Unfocused tilix window transparency Status in yaru-theme package in Ubuntu: Fix Released Bug description: With Yaru theme the background transparency of unfocused Tilix Windows is removed. I mean, when a Tilix terminal is focused, the transparency settings is correctly applied to the background. But, if the windows loose the focus, the background became opaque. With other gtk theme like adwaita or arc ... we don't have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gtk 18.10.6 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 23 01:24:28 2018 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1809564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854565] [NEW] Mouse (not touchpad) right click acts as left click
Public bug reported: Ubuntu 18.04.3 LTS (Please note this refers to an actual USB mouse on a Desktop system, _not_ a Touchpad) What happens: Clicking the the right button of my mouse shows the context menu but then sometimes also acts as a left click. Steps to reproduce: - open a web page move the mouse pointer over a link - click the right button (keep clicking the right button if the bug doesn't manifest immediately) - at a certain (random) point, the link is followed as if a left click was issued The bug is erratic but always reproducible (it is not always the _first_ right-click to be misinterpreted as a left one, but after a few tries it always does). What Should happen: A right click should never be interpreted as a left one. This is a very basic UI interaction. Extra information: Tried different USB mice, it is not a hardware error. Possibly related: the context menu sometimes appears very far from the actual position of the mouse cursor. What I tried: I tried disabling mouse click emulation via gnome-tweaks (see attachment). Nothing changed. ** Affects: gsettings-desktop-schemas (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2019-11-30 12-02-18.png" https://bugs.launchpad.net/bugs/1854565/+attachment/5308869/+files/Screenshot%20from%202019-11-30%2012-02-18.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1854565 Title: Mouse (not touchpad) right click acts as left click Status in gsettings-desktop-schemas package in Ubuntu: New Bug description: Ubuntu 18.04.3 LTS (Please note this refers to an actual USB mouse on a Desktop system, _not_ a Touchpad) What happens: Clicking the the right button of my mouse shows the context menu but then sometimes also acts as a left click. Steps to reproduce: - open a web page move the mouse pointer over a link - click the right button (keep clicking the right button if the bug doesn't manifest immediately) - at a certain (random) point, the link is followed as if a left click was issued The bug is erratic but always reproducible (it is not always the _first_ right-click to be misinterpreted as a left one, but after a few tries it always does). What Should happen: A right click should never be interpreted as a left one. This is a very basic UI interaction. Extra information: Tried different USB mice, it is not a hardware error. Possibly related: the context menu sometimes appears very far from the actual position of the mouse cursor. What I tried: I tried disabling mouse click emulation via gnome-tweaks (see attachment). Nothing changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1854565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
On GNOME vanilla session, enabling both extensions it shows a different behavior. Everything seems to work properly except that GNOME-Tweaks fails to start (Failed to register: Timeout was reached) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew Status in gnome-shell package in Ubuntu: Confirmed Bug description: First reported here https://discourse.ubuntu.com/t/installing-just- one-extension-makes-ubuntu-eoan-to-fail/12816 Steps 1. I tried first to disabled default Desktop Icons extension(1) 2. I installed "Desktop Icons NG" from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ 3. Tested the extension was properly working (DnD, open folders) OK 4. Opened the Activity view: stuck in this view At this stage there is no way to exit from the activity view. Arrow keys work fine for moving the selection on open window, search works fine as well, but pressing Enter key does nothing, as well as clicking on the close window X does not kill the windows. Logging out is the only way to recover, until Activity view is opened again. Reproduced on Eoan in a VM, while it is not reproducible on Fedora 29 (currently I can't test the latest fedora, but the original report made more tests and it seems reproducible in Eoan only). This extension provides some more common features for desktop icons, so it is likely to be installed more in the future. Note: 1. The default desktop icons extension looks always disabled (GNOME tweaks switch is off), even if it's actually working, so I just switched the visibility of the icons off from default Desktop Icons settings. This very likely did not disable the extension, but it's likely what a normal user would do. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 11:18:50 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846871] Re: Desktop Icons NG shell extension breaks Activities vew
It seems to work fine on Ubuntu using GNOME vanilla session. I don't know if it has been reported already to Carlos (I didn't know he was the maintainer), but I wonder if it's possible to fix the status of Desktop Icon on Ubuntu, since it doesn't seem to be possible to disable it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew Status in gnome-shell package in Ubuntu: Confirmed Bug description: First reported here https://discourse.ubuntu.com/t/installing-just- one-extension-makes-ubuntu-eoan-to-fail/12816 Steps 1. I tried first to disabled default Desktop Icons extension(1) 2. I installed "Desktop Icons NG" from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ 3. Tested the extension was properly working (DnD, open folders) OK 4. Opened the Activity view: stuck in this view At this stage there is no way to exit from the activity view. Arrow keys work fine for moving the selection on open window, search works fine as well, but pressing Enter key does nothing, as well as clicking on the close window X does not kill the windows. Logging out is the only way to recover, until Activity view is opened again. Reproduced on Eoan in a VM, while it is not reproducible on Fedora 29 (currently I can't test the latest fedora, but the original report made more tests and it seems reproducible in Eoan only). This extension provides some more common features for desktop icons, so it is likely to be installed more in the future. Note: 1. The default desktop icons extension looks always disabled (GNOME tweaks switch is off), even if it's actually working, so I just switched the visibility of the icons off from default Desktop Icons settings. This very likely did not disable the extension, but it's likely what a normal user would do. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 11:18:50 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846871] [NEW] Desktop Icons NG shell extension breaks Activities vew
Public bug reported: First reported here https://discourse.ubuntu.com/t/installing-just-one- extension-makes-ubuntu-eoan-to-fail/12816 Steps 1. I tried first to disabled default Desktop Icons extension(1) 2. I installed "Desktop Icons NG" from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ 3. Tested the extension was properly working (DnD, open folders) OK 4. Opened the Activity view: stuck in this view At this stage there is no way to exit from the activity view. Arrow keys work fine for moving the selection on open window, search works fine as well, but pressing Enter key does nothing, as well as clicking on the close window X does not kill the windows. Logging out is the only way to recover, until Activity view is opened again. Reproduced on Eoan in a VM, while it is not reproducible on Fedora 29 (currently I can't test the latest fedora, but the original report made more tests and it seems reproducible in Eoan only). This extension provides some more common features for desktop icons, so it is likely to be installed more in the future. Note: 1. The default desktop icons extension looks always disabled (GNOME tweaks switch is off), even if it's actually working, so I just switched the visibility of the icons off from default Desktop Icons settings. This very likely did not disable the extension, but it's likely what a normal user would do. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 11:18:50 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1846871 Title: Desktop Icons NG shell extension breaks Activities vew Status in gnome-shell package in Ubuntu: New Bug description: First reported here https://discourse.ubuntu.com/t/installing-just- one-extension-makes-ubuntu-eoan-to-fail/12816 Steps 1. I tried first to disabled default Desktop Icons extension(1) 2. I installed "Desktop Icons NG" from https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ 3. Tested the extension was properly working (DnD, open folders) OK 4. Opened the Activity view: stuck in this view At this stage there is no way to exit from the activity view. Arrow keys work fine for moving the selection on open window, search works fine as well, but pressing Enter key does nothing, as well as clicking on the close window X does not kill the windows. Logging out is the only way to recover, until Activity view is opened again. Reproduced on Eoan in a VM, while it is not reproducible on Fedora 29 (currently I can't test the latest fedora, but the original report made more tests and it seems reproducible in Eoan only). This extension provides some more common features for desktop icons, so it is likely to be installed more in the future. Note: 1. The default desktop icons extension looks always disabled (GNOME tweaks switch is off), even if it's actually working, so I just switched the visibility of the icons off from default Desktop Icons settings. This very likely did not disable the extension, but it's likely what a normal user would do. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 11:18:50 2019 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845680] [NEW] [UIFe] Firefox active menu items are invisible in Yaru "Ambiance"
Public bug reported: First reported here https://github.com/ubuntu/yaru/issues/1548 In Yaru "Ambiance", Firefox's "menuitem:hover" lacks of specific background and color styling and the default values make the menuitem:hover label invisible (dark text on dark background). The same issue does not occur in Yaru-light and Yaru-dark. The fix is limited to Firefox only (thanks to specific css target MozillaGtkWidget) and only active in Yaru ambiance, so no negative impact is expected. Proposed fix here https://github.com/ubuntu/yaru/pull/1549 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1845680 Title: [UIFe] Firefox active menu items are invisible in Yaru "Ambiance" Status in yaru-theme package in Ubuntu: New Bug description: First reported here https://github.com/ubuntu/yaru/issues/1548 In Yaru "Ambiance", Firefox's "menuitem:hover" lacks of specific background and color styling and the default values make the menuitem:hover label invisible (dark text on dark background). The same issue does not occur in Yaru-light and Yaru-dark. The fix is limited to Firefox only (thanks to specific css target MozillaGtkWidget) and only active in Yaru ambiance, so no negative impact is expected. Proposed fix here https://github.com/ubuntu/yaru/pull/1549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1845680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827948] Re: Use libreoffice-style-breeze as the default icon theme
On one side, breeze icons might look a bit colder, but they're actually graphically closer to yaru's symbolic icons -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1827948 Title: Use libreoffice-style-breeze as the default icon theme Status in libreoffice package in Ubuntu: New Bug description: The Yaru icon theme uses 1 pixel strokes for its symbolic icon set. So do the breeze icons for libreoffice. All in all does the breeze icon set for libre office fit very good to the look of the Yaru icons. https://i.imgur.com/tgioycv.png https://i.imgur.com/WwKvjMh.png Thus I would suggest to use it as the default icon set in Ubuntu to guarantee a consistent look and feel across the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820767] [NEW] UIFe for late GNOME 3.32 icon name changes
Public bug reported: The following GNOME 3.32 app were released after UI Freeze (with no previous 3.31 releases) with a different app icon name. - preferences-desktop-font → org.gnome.font-viewer - gnome-characters → org.gnome.Characters - applets-screenshooter → org.gnome.Screenshot Except for gnome-screenshot, these releases also adapt to the new GNOME menu guidelines so I think we do need to do these updates. Without the proposed change, those applications will appear with GNOME upstream icons, instead of the Yaru ones, this is why I consider this a UI Freeze exception. This change is addressed adding new symlinks between the new and the old icon names, without removing the latters, so that the risk of regression issues is really low, if not zero - if any of the applications above should appear with the old icon name, the old symlink will provide the correct icon name - if any of the applications above should appear with an icon name different than the old or the new, upstream icon will be used anyway as it would be without this change Finally, the change has been tested installing the affected applications from [[https://launchpad.net/~jbicha/+archive/ubuntu/temp332/+packages|here]] ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Description changed: - The following GNOME 3.32 app was released after UI Freeze (with no + The following GNOME 3.32 app were released after UI Freeze (with no previous 3.31 releases) with a different app icon name. - preferences-desktop-font → org.gnome.font-viewer - gnome-characters → org.gnome.Characters - applets-screenshooter → org.gnome.Screenshot Except for gnome-screenshot, these releases also adapt to the new GNOME menu guidelines so I think we do need to do these updates. Without the proposed change, those applications will appear with GNOME upstream icons, instead of the Yaru ones, this is why I consider this a UI Freeze exception. This change is addressed adding new symlinks between the new and the old icon names, without removing the latters, so that the risk of regression issues is really low, if not zero - - if any of the applications above should appear with the old icon name, the old symlink will provide the correct icon name - - if any of the applicaitons above should appear wiht an icon name different than the old or the new, upstream icon will be used anyway as it would be without this change + - if any of the applications above should appear with the old icon name, the old symlink will provide the correct icon name + - if any of the applicaitons above should appear wiht an icon name different than the old or the new, upstream icon will be used anyway as it would be without this change Finally, the change has been tested using installing the affected applications from [[https://launchpad.net/~jbicha/+archive/ubuntu/temp332/+packages|here]] ** Description changed: The following GNOME 3.32 app were released after UI Freeze (with no previous 3.31 releases) with a different app icon name. - preferences-desktop-font → org.gnome.font-viewer - gnome-characters → org.gnome.Characters - applets-screenshooter → org.gnome.Screenshot Except for gnome-screenshot, these releases also adapt to the new GNOME menu guidelines so I think we do need to do these updates. Without the proposed change, those applications will appear with GNOME upstream icons, instead of the Yaru ones, this is why I consider this a UI Freeze exception. This change is addressed adding new symlinks between the new and the old icon names, without removing the latters, so that the risk of regression issues is really low, if not zero - if any of the applications above should appear with the old icon name, the old symlink will provide the correct icon name - - if any of the applicaitons above should appear wiht an icon name different than the old or the new, upstream icon will be used anyway as it would be without this change + - if any of the applications above should appear with an icon name different than the old or the new, upstream icon will be used anyway as it would be without this change Finally, the change has been tested using installing the affected applications from [[https://launchpad.net/~jbicha/+archive/ubuntu/temp332/+packages|here]] ** Description changed: The following GNOME 3.32 app were released after UI Freeze (with no previous 3.31 releases) with a different app icon name. - preferences-desktop-font → org.gnome.font-viewer - gnome-characters → org.gnome.Characters - applets-screenshooter → org.gnome.Screenshot Except for gnome-screenshot, these releases also adapt to the new GNOME menu guidelines so I think we do need to do these updates. Without the proposed change, those applications will appear with GNOME upstream icons, instead of the Yaru ones, this is why I consider this a UI Fre
[Desktop-packages] [Bug 1796548] Re: [regression] New windows are all centred
I agree with amano, I do expect the window I want to work on to present itsel just in front of me. The good thing I see in auto-placement is only that it looks for free space (if my understanding is correct), so the best solution for me would be to mix this two features -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1796548 Title: [regression] New windows are all centred Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: In a fresh cosmic installation new windows all appear in the same place; the middle of the screen. This makes opening multiple windows annoying. WORKAROUND: Gnome Tweaks > Windows > Center New Windows = OFF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1796548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
FYI, HDMI output works when I switch to a terminal using CTRL_ALT_F3. It seems to not work only in graphics mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x25b) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.75KHz v: height 1080 start 1084 end 1094 total 1125
[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I have the same issue here: xrandr output: Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192 LVDS-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 353mm x 198mm 1366x768 60.00*+ 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) SVIDEO-1 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.885
[Desktop-packages] [Bug 1803521] [NEW] gnome-initial-setup uses wrong icon
Public bug reported: The "Welcome to Ubuntu" application uses the circle of friends Ubuntu logo, while it is expected to use a Suru icon from Yaru theme. version: - Ubuntu 18.10 - gnome-initial-setup: 3.30.0-1ubuntu3 Steps to Reproduce the Problem 1. Install Ubuntu 2. Reboot 3. Check the icon used in the dock This is the existing icon https://github.com/ubuntu/yaru/blob/master/icons/src/fullcolor/apps/welcome-app.svg Which is symlinked to https://github.com/ubuntu/yaru/blob/master/icons/Suru/48x48/apps/ubuntu-welcome-app.png ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1803521 Title: gnome-initial-setup uses wrong icon Status in gnome-initial-setup package in Ubuntu: New Bug description: The "Welcome to Ubuntu" application uses the circle of friends Ubuntu logo, while it is expected to use a Suru icon from Yaru theme. version: - Ubuntu 18.10 - gnome-initial-setup: 3.30.0-1ubuntu3 Steps to Reproduce the Problem 1. Install Ubuntu 2. Reboot 3. Check the icon used in the dock This is the existing icon https://github.com/ubuntu/yaru/blob/master/icons/src/fullcolor/apps/welcome-app.svg Which is symlinked to https://github.com/ubuntu/yaru/blob/master/icons/Suru/48x48/apps/ubuntu-welcome-app.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1803521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799217] [NEW] Yaru-dark packaged even if not complete, nor necessary
Public bug reported: yaru-theme package for Cosmic Cuttlefish includes 'Yaru-dark', which is not complete (it lacks of gtk2 folder). Note, as discussed on IRC, in order to support applications that prefer dark variant, /usr/share/themes/Yaru/gtk-3.0/gtk-dark.css is enough ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1799217 Title: Yaru-dark packaged even if not complete, nor necessary Status in yaru-theme package in Ubuntu: New Bug description: yaru-theme package for Cosmic Cuttlefish includes 'Yaru-dark', which is not complete (it lacks of gtk2 folder). Note, as discussed on IRC, in order to support applications that prefer dark variant, /usr/share/themes/Yaru/gtk-3.0/gtk-dark.css is enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1799217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 958139] Re: nautilus crashed with SIGSEGV in nautilus_icon_canvas_item_get_drag_surface()
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete ** Changed in: nautilus Status: New => Incomplete -- 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/958139 Title: nautilus crashed with SIGSEGV in nautilus_icon_canvas_item_get_drag_surface() Status in Nautilus: Incomplete Status in nautilus package in Ubuntu: Incomplete Status in nautilus package in Fedora: Won't Fix Bug description: I was doing one by one delete in different folders simply by hitting DEL. The mouse pointer changed in nautilus. And then it crashes. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.91-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Sat Mar 17 21:34:32 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: org.gnome.nautilus.window-state geometry '1057x715+65+24' org.gnome.nautilus.window-state side-pane-view 'tree' org.gnome.nautilus.window-state sidebar-width 236 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316) ProcCmdline: nautilus ProcEnviron: LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x50394f: mov(%rbx),%rdx PC (0x0050394f) ok source "(%rbx)" (0x0002) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/958139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719355] Re: Switcher widget background goes outside its border
** Changed in: ubuntu-themes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1719355 Title: Switcher widget background goes outside its border Status in Ubuntu theme: Fix Released Status in Ubuntu UX: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Artful: Fix Released Bug description: [Impact] In both Ambiance and Radiance themes, the switcher background is visible outside the widget border when inside a headerbar. See picture from Gnome Control Settings -> Search [Test case] 1. Open Gnome Control Settings -> Search 2. Ensure that no extra border is around the switcher (especially in the headerbar) [Regression potential] Switchers borders are incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1719355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732525] Re: drag and drop on Desktop keeps stuck with hand icon
This bug is reported upstream here https://gitlab.gnome.org/GNOME/nautilus/issues/29 however launchpad does not recognize gitlab bug tracker ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1732525 Title: drag and drop on Desktop keeps stuck with hand icon Status in nautilus package in Ubuntu: Confirmed Bug description: I have the following bug with a clean install of Ubuntu 17.10. When I try to drag a file or folder from my desktop to an open nautilus window the file or folder doesn't get moved and instead the mouse keeps being stuck in the hand icon. This meakes the system merely usable anymore since I can open applications like firefox but can not click any buttons in it except the quit buttons. I have to reboot the system to get it to work again. This happens on every try. see also a similar report: https://askubuntu.com/questions/975000 /dragn-drop-from-desktop-mouse-stuck-in-hand-icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1732525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705492] Re: gnome-shell crashes with SIGSEGV in meta_plugin_manager_xevent_filter() from x_event_source_dispatch()
This bug happens to me quite frequently (from once to three times per day) and it's quite annoying. It appears to be random even if sometimes it happens when I try to open the notification window (in the topbar clicking on the date time) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705492 Title: gnome-shell crashes with SIGSEGV in meta_plugin_manager_xevent_filter() from x_event_source_dispatch() Status in gnome-shell package in Ubuntu: Confirmed Bug description: I can login using unity but when I choose gnome it takes while and the screen turns black and eventually it brings me back to the login page. this only started happening after upgrading to ubuntu 17.10. I've tried removing the .Xauthority file. I've also tried purging Nvidia drivers. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Jul 20 08:43:48 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-12-13 (218 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6ad2d03790 : mov0x8(%rdi),%rdi PC (0x7f6ad2d03790) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_plugin_manager_xevent_filter () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_plugin_manager_xevent_filter() UpgradeStatus: Upgraded to artful on 2017-05-22 (58 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705492] Re: gnome-shell crashes with SIGSEGV in meta_plugin_manager_xevent_filter() from x_event_source_dispatch()
** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705492/+attachment/5009267/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705492 Title: gnome-shell crashes with SIGSEGV in meta_plugin_manager_xevent_filter() from x_event_source_dispatch() Status in gnome-shell package in Ubuntu: Confirmed Bug description: I can login using unity but when I choose gnome it takes while and the screen turns black and eventually it brings me back to the login page. this only started happening after upgrading to ubuntu 17.10. I've tried removing the .Xauthority file. I've also tried purging Nvidia drivers. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Jul 20 08:43:48 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-12-13 (218 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6ad2d03790 : mov0x8(%rdi),%rdi PC (0x7f6ad2d03790) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_plugin_manager_xevent_filter () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_plugin_manager_xevent_filter() UpgradeStatus: Upgraded to artful on 2017-05-22 (58 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694303] Re: Font issues in Zesty
Confirmed on light-themes 16.10+17.04.20170406-0ubuntu1 not reproducible on 16.10+17.10.20170518-0ubuntu1 ** Package changed: gitg (Ubuntu) => light-themes (Ubuntu) ** Changed in: light-themes (Ubuntu) Status: New => Confirmed -- 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/1694303 Title: Font issues in Zesty Status in light-themes package in Ubuntu: Confirmed Bug description: I have a couple of font issues with gitg (version: 3.23.0-1) in Zesty: - commit description text is white (which is unreadable on light gray background in the default Ubuntu theme) - diffs are not in monospaced font anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1694303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1709064] Re: evince doesn't start in artful beta
Hi there, I applied the fix form here [https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=827335#54] and with that evince starts BUT with a new error, that I think it's also apparmor related: (evince:14816): Gtk-WARNING **: Attempting to read the recently used resources file at '/home/carlo/.local/share/recently-used.xbel', but the parser failed: Failed to open file “/home/carlo/.local/share/recently- used.xbel”: Permission denied. Carlo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta Status in evince package in Ubuntu: Confirmed Bug description: Can't open a pdf with evince as nothing happens after clicking twice on the file. Starting from terminal the following error is occurs: ''' (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted (core dumped) ''' carlo@thinkpad:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 carlo@thinkpad:~$ apt-cache policy evince evince: Installed: 3.24.1-0ubuntu1 Candidate: 3.24.1-0ubuntu1 Version table: *** 3.24.1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 7 13:24:59 2017 InstallationDate: Installed on 2017-08-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1709064] Re: evince doesn't start in artful beta
I made some tests, and it also fails on wayland. I also changed the system to the default icon theme and cursor icon but the problem still persists. Cheers, Carlo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta Status in evince package in Ubuntu: Confirmed Bug description: Can't open a pdf with evince as nothing happens after clicking twice on the file. Starting from terminal the following error is occurs: ''' (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted (core dumped) ''' carlo@thinkpad:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 carlo@thinkpad:~$ apt-cache policy evince evince: Installed: 3.24.1-0ubuntu1 Candidate: 3.24.1-0ubuntu1 Version table: *** 3.24.1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 7 13:24:59 2017 InstallationDate: Installed on 2017-08-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1709064] [NEW] evince doesn't start in artful beta
Public bug reported: Can't open a pdf with evince as nothing happens after clicking twice on the file. Starting from terminal the following error is occurs: ''' (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted (core dumped) ''' carlo@thinkpad:~$ lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 carlo@thinkpad:~$ apt-cache policy evince evince: Installed: 3.24.1-0ubuntu1 Candidate: 3.24.1-0ubuntu1 Version table: *** 3.24.1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 7 13:24:59 2017 InstallationDate: Installed on 2017-08-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful beta wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta Status in evince package in Ubuntu: New Bug description: Can't open a pdf with evince as nothing happens after clicking twice on the file. Starting from terminal the following error is occurs: ''' (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted (core dumped) ''' carlo@thinkpad:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 carlo@thinkpad:~$ apt-cache policy evince evince: Installed: 3.24.1-0ubuntu1 Candidate: 3.24.1-0ubuntu1 Version table: *** 3.24.1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 7 13:24:59 2017 InstallationDate: Installed on 2017-08-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706916] Re: 'new document' option missing in partition window
Could you update problem description so that it reflects the right issue? -- 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/1706916 Title: 'new document' option missing in partition window Status in nautilus package in Ubuntu: New Bug description: right click on window of a folder in a mounted partition does not show 'new document' also if /home/templates is populated. right click on window of a local folder works fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.24.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jul 27 11:44:10 2017 InstallationDate: Installed on 2017-07-18 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1706916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706916] Re: 'new document' option missing in partition window
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please, could you report the permission you have in the mounted partition? -- 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/1706916 Title: 'new document' option missing in partition window Status in nautilus package in Ubuntu: New Bug description: right click on window of a folder in a mounted partition does not show 'new document' also if /home/templates is populated. right click on window of a local folder works fine. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.24.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jul 27 11:44:10 2017 InstallationDate: Installed on 2017-07-18 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1706916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1025488] ✈I've found some great stuff
** Attachment added: "B3FEF59A6A9C650F.jpg" https://bugs.launchpad.net/bugs/1025488/+attachment/4920167/+files/B3FEF59A6A9C650F.jpg ** Attachment added: "B3FEF59A6A9C650F1.jpg" https://bugs.launchpad.net/bugs/1025488/+attachment/4920168/+files/B3FEF59A6A9C650F1.jpg ** Attachment added: "B3FEF59A6A9C650F2.jpg" https://bugs.launchpad.net/bugs/1025488/+attachment/4920169/+files/B3FEF59A6A9C650F2.jpg ** Attachment added: "B3FEF59A6A9C650F3.jpg" https://bugs.launchpad.net/bugs/1025488/+attachment/4920170/+files/B3FEF59A6A9C650F3.jpg ** Attachment added: "B3FEF59A6A9C650F4.png" https://bugs.launchpad.net/bugs/1025488/+attachment/4920171/+files/B3FEF59A6A9C650F4.png ** Attachment added: "B3FEF59A6A9C650F5.png" https://bugs.launchpad.net/bugs/1025488/+attachment/4920172/+files/B3FEF59A6A9C650F5.png ** Attachment added: "B3FEF59A6A9C650F6.png" https://bugs.launchpad.net/bugs/1025488/+attachment/4920173/+files/B3FEF59A6A9C650F6.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1025488 Title: fglrx (not installed): fglrx kernel module failed to build [error: implicit declaration of function ‘do_mmap’] Status in fglrx-installer package in Ubuntu: Invalid Status in fglrx-installer-updates package in Ubuntu: Invalid Bug description: trying to install ATI drivers ProblemType: Package DistroRelease: Ubuntu 12.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.1: ApportVersion: 2.3-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 3.5.0-4-generic Date: Mon Jul 16 20:47:33 2012 DistUpgraded: 2012-07-16 16:38:43,731 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.2.0-23-generic, x86_64: installed bcmwl, 5.100.82.112+bdcom, 3.5.0-4-generic, x86_64: installed fglrx, 8.980: added GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1641] Advanced Micro Devices [AMD] nee ATI Robson CE [AMD Radeon HD 6300 Series] [1002:68e4] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1641] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-4-generic root=UUID=051fedbd-e1fd-4b72-b1c0-4aa7cf7c4578 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UpgradeStatus: Upgraded to quantal on 2012-07-16 (0 days ago) dmi.bios.date: 03/24/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1641 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.27:bd03/24/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058A12242B1020100:rvnHewlett-Packard:rn1641:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 058A12242B1020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.37-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~really6.14.4-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1025488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1131246] many beautiful things
*** This bug is a duplicate of bug 1025488 *** https://bugs.launchpad.net/bugs/1025488 ** Attachment added: "FF56D677208203D3.jpg" https://bugs.launchpad.net/bugs/1131246/+attachment/4920174/+files/FF56D677208203D3.jpg ** Attachment added: "FF56D677208203D31.jpg" https://bugs.launchpad.net/bugs/1131246/+attachment/4920175/+files/FF56D677208203D31.jpg ** Attachment added: "FF56D677208203D32.jpg" https://bugs.launchpad.net/bugs/1131246/+attachment/4920176/+files/FF56D677208203D32.jpg ** Attachment added: "FF56D677208203D33.jpg" https://bugs.launchpad.net/bugs/1131246/+attachment/4920177/+files/FF56D677208203D33.jpg ** Attachment added: "FF56D677208203D34.png" https://bugs.launchpad.net/bugs/1131246/+attachment/4920178/+files/FF56D677208203D34.png ** Attachment added: "FF56D677208203D35.png" https://bugs.launchpad.net/bugs/1131246/+attachment/4920179/+files/FF56D677208203D35.png ** Attachment added: "FF56D677208203D36.png" https://bugs.launchpad.net/bugs/1131246/+attachment/4920180/+files/FF56D677208203D36.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1131246 Title: fglrx (not installed): fglrx kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: trying to install catalyst 12.4 un ubuntu 12.10 I get this error ProblemType: Package DistroRelease: Ubuntu 12.10 Package: fglrx 2:8.961-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSKernelVersion: 3.5.0-21-generic Date: Thu Feb 21 16:24:35 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: fglrx, 8.961: added GraphicsCard: Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 7400 Series] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:249f] InstallationDate: Installed on 2012-11-26 (86 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard p6-2312el MarkForUpload: True PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=2e9203a8-b83b-4542-9464-0573af420737 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number of failed request: 25 Current serial number in output stream: 26 UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 08/29/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.07 dmi.board.name: 2ADA dmi.board.vendor: Foxconn dmi.board.version: 1.00 dmi.chassis.asset.tag: CZC2388M2J dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.07:bd08/29/2012:svnHewlett-Packard:pnp6-2312el:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6-2312el dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1131246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246527] Re: Gnome System Monitor graphs miss their horizontal and vertical axes
Not reproducible on Xubuntu 16.04.2 i386 ** Attachment added: "picture of gnome-system-monitor" https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1246527/+attachment/4916855/+files/xubuntu32b-monitor.png ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1246527 Title: Gnome System Monitor graphs miss their horizontal and vertical axes Status in gnome-system-monitor package in Ubuntu: Invalid Bug description: System: Xubuntu 13.10, 32 bit, fully patched Gnome System Monitor package installed: gnome-system-monitor 3.8.2.1-2 CPU: Intel Atom N270 (Netbook) Graphics (output from lspci | grep VGA): 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) Issue: System Monitor > Resources tab presents three graphs (one each for "CPU History", "Memory and Swap History", and "Network History"). Each of these graphs normally has a narrow border on all four edges, a labeled horizontal axis, a labeled vertical axis, and the graph itself with the moving traces on a white field with a grid. However, in each of the graphs, the horizontal and the vertical axes as well as the borders are missing. The areas where these elements should be positioned are instead filled with a uniform black colour. (The fields with the moving traces are unaffected and behave as expected.) Note: This bug appears irrespective of the chosen combination of settings (including varying the update interval) in the Preferences panel > Resources tab of System Monitor. Note: This same bug was also present in gnome-system-monitor under xubuntu 11.10. It had been patched in xubuntu 12.04, but it reappeared in xubuntu 13.04 and remains in xubuntu 13.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1246527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Re: USB Modem not displayed in network manager
Marking this as incomplete since some information are missing ** Changed in: modemmanager (Ubuntu) Status: New => Incomplete ** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Changed in: plasma-nm (Ubuntu) Status: New => Incomplete -- 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/1686573 Title: USB Modem not displayed in network manager Status in modemmanager package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Status in plasma-nm package in Ubuntu: Incomplete Bug description: 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
[Desktop-packages] [Bug 1413117] Re: icon captions info on desktop don't disappear
Hi Sebastien, the original issue was reported against "nautilus 3.10" which can't be selected on the upstream bug tracker (only >=3.14), and in the newer version 3.18 I cannot reproduce it. What do you suggest to do? -- 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/1413117 Title: icon captions info on desktop don't disappear Status in nautilus package in Ubuntu: New Bug description: In nautilus, when I go to Edit -> Preferences -> Display -> icon captions, and change the highest order (first one) from None to Type (or anything else), this change is not applied to desktop icons and nothing happens to them. And when I set it back to None, Type captions (or whatever I selected at first) appear under desktop icons. This problem only occurs for desktop icons. It works fine for icons in other directories. Actually I expect that when I change icon captions from None to Type, type information of each file or directory appears under desktop icons, but nothing happens. And furthermore I expect that when I change it back to None, type information disappears, but they appear. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: Unity Date: Wed Jan 21 12:01:28 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-12-08 (409 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-09-08 (135 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1413117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1413117] Re: icon captions info on desktop don't disappear
This is a quite old bug. I tried with nautilus 1:3.18.4.is.4.14.3-0ubuntu5 on Ubuntu 16.04. I can confirm that the special folders like "Home", "Network" and "Trash" do not show icon caption, but I do not know if this is intended or not, since the caption does not appear even when "icon caption" option is set back to None. Finally, all the other files or folders created on the Desktop, show correctly the expected caption. If the last behavior is not intended for the special icons, I think this bug can be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1413117 Title: icon captions info on desktop don't disappear Status in nautilus package in Ubuntu: New Bug description: In nautilus, when I go to Edit -> Preferences -> Display -> icon captions, and change the highest order (first one) from None to Type (or anything else), this change is not applied to desktop icons and nothing happens to them. And when I set it back to None, Type captions (or whatever I selected at first) appear under desktop icons. This problem only occurs for desktop icons. It works fine for icons in other directories. Actually I expect that when I change icon captions from None to Type, type information of each file or directory appears under desktop icons, but nothing happens. And furthermore I expect that when I change it back to None, type information disappears, but they appear. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.4 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic i686 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: Unity Date: Wed Jan 21 12:01:28 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-12-08 (409 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-09-08 (135 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1413117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding
Confirmed upstream and patch proposed ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1700319 Title: GTK3 menus don't work over SSH forwarding Status in Ubuntu: Confirmed Bug description: When connecting remotely (either SSH X11 forwarding or direct to X11 server), drop down menus do not display properly. Bug upstream in gtk3: https://bugzilla.gnome.org/show_bug.cgi?id=780101 Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3 Server: Windows 10 Cygwin/X 1.19.2-1 Programs exhibiting this problem: evince 3.24.0 (and any other gtk3 apps with menus along the top). Patch applied to gtk3 in cygwin to fix this problem and attached to this post: https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch Console errors: (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed (evince:7390): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: The name org.freedesktop.portal.Desktop is not owned (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu) *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1700319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
** Bug watch added: GNOME Bug Tracker #784095 https://bugzilla.gnome.org/show_bug.cgi?id=784095 ** Also affects: banshee via https://bugzilla.gnome.org/show_bug.cgi?id=784095 Importance: Unknown Status: Unknown -- 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/1699800 Title: Extension Library Watcher causes Banshee to stall Status in Banshee: Unknown Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
As workaround to take back control of banshee without reinstalling it $ sed -i 's/Addin id="Banshee.LibraryWatcher,1.0" enabled="True"/Addin id="Banshee.LibraryWatcher,1.0" enabled="False"/g' $HOME/.config/banshee-1/addin-db-001/config.xml -- 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/1699800 Title: Extension Library Watcher causes Banshee to stall Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
Basically, edit file $HOME/.config/banshee-1/addin-db-001/config.xml changing the value of Banshee.LibraryWatcher,1.0 to False -- 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/1699800 Title: Extension Library Watcher causes Banshee to stall Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699800] Re: Extension Library Watcher causes Banshee to stall
Confirmed on Ubuntu 16.10 ** Changed in: banshee (Ubuntu) Status: New => Confirmed -- 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/1699800 Title: Extension Library Watcher causes Banshee to stall Status in banshee package in Ubuntu: Confirmed Bug description: The extension Library Watcher causes Banshee to stall and do nothing even when closed and ran again. To reproduce this bug go to Preferences in the Edit menu and there in the Extensions tab click the checkmark for Library Watcher. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: banshee 2.9.0+really2.6.2-7ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 22 09:45:26 2017 InstallationDate: Installed on 2017-06-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1699800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567796] Re: It is sometimes unable to find DELL WWAN module.
Updated the description with the information requested in SRU template ** Description changed: I have a DELL WWAN module (DW5580) on my platform. Normally it could be detect and used in Ubuntu 16.04 daily image. However it is sometimes unusable and can not be detected. After debugging, we found there is an upstream patch that can fix the issue: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: Installed: 1.4.12-1ubuntu1 Candidate: 1.4.12-1ubuntu1 Version table: *** 1.4.12-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status + + + + * 2017-06-20 Update details for SRU + + [Impact] + + DELL WWAN module (DW5580) is sometimes unusable and can not be detected + by ModemManager. + + The fix consisted in the correct initialization of a "retry" variable in + modem's probing. Without this initialization, the "retry" variable might + assume random big values, forcing the modem to retry the same step a + semi-infinite number of times. + + + [Test Case] + + 1. Start/restart the ModemManager service with debug messages enabled + + a. Open ModemManager.service file and add the flag --debug to the ExecStart entry + + ExecStart=/usr/local/sbin/ModemManager --debug + + b. run systemctl daemon-reload + c. run systemctl restart Modemmanager + + 2. Connect Dell WWAN module DW5580 (if the modem is integrated, skip this step) + 3. Open ModemManager logs: + + journalctl -fu ModemManager + + 4. ModemManager logs show that the service is continuously sending AT + command "AT+CGMI" preventing the modem to be recognized + + + [Regression Potential] + + Considering the nature of the fix (a variable that was not initialized), + I can not think of a real potential regression and the patch has been + tested and showed no issues so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1567796 Title: It is sometimes unable to find DELL WWAN module. Status in OEM Priority Project: Incomplete Status in modemmanager package in Ubuntu: Fix Released Bug description: I have a DELL WWAN module (DW5580) on my platform. Normally it could be detect and used in Ubuntu 16.04 daily image. However it is sometimes unusable and can not be detected. After debugging, we found there is an upstream patch that can fix the issue: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: Installed: 1.4.12-1ubuntu1 Candidate: 1.4.12-1ubuntu1 Version table: *** 1.4.12-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status * 2017-06-20 Update details for SRU [Impact] DELL WWAN module (DW5580) is sometimes unusable and can not be detected by ModemManager. The fix consisted in the correct initialization of a "retry" variable in modem's probing. Without this initialization, the "retry" variable might assume random big values, forcing the modem to retry the same step a semi-infinite number of times. [Test Case] 1. Start/restart the ModemManager service with debug messages enabled a. Open ModemManager.service file and add the flag --debug to the ExecStart entry ExecStart=/usr/local/sbin/ModemManager --debug b. run systemctl daemon-reload c. run systemctl restart Modemmanager 2. Connect Dell WWAN module DW5580 (if the modem is integrated, skip this step) 3. Open ModemManager logs: journalctl -fu ModemManager 4. ModemManager logs show that the service is continuously sending AT command "AT+CGMI" preventing the modem to be recognized [Regression Potential] Considering the nature of the fix (a variable that was not initialized), I can not think of a real potential regression and the patch has been tested and showed no issues so far. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1567796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567796] Re: It is sometimes unable to find DELL WWAN module.
I can try to do it for sure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1567796 Title: It is sometimes unable to find DELL WWAN module. Status in OEM Priority Project: Incomplete Status in modemmanager package in Ubuntu: Fix Released Bug description: I have a DELL WWAN module (DW5580) on my platform. Normally it could be detect and used in Ubuntu 16.04 daily image. However it is sometimes unusable and can not be detected. After debugging, we found there is an upstream patch that can fix the issue: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: Installed: 1.4.12-1ubuntu1 Candidate: 1.4.12-1ubuntu1 Version table: *** 1.4.12-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1567796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650792] Re: Ubuntu 16.04.1 System policy prevents modification of network settings for all users
*** This bug is a duplicate of bug 964705 *** https://bugs.launchpad.net/bugs/964705 Thank you for taking the time to report this bug and helping to make Ubuntu better. I marked this bug as duplicate of bug #964705. Could you please take some time to open one more bug for the udev rule you added? ** This bug has been marked a duplicate of bug 964705 System policy prevents modification of network settings for all users -- 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/1650792 Title: Ubuntu 16.04.1 System policy prevents modification of network settings for all users Status in modemmanager package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Same bug as described for Ubuntu 15.04 (see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/964705) is still in my Ubuntu 16.04.1! My workaround is simple but strange: After switching on my notebook, booting into Ubuntu 16.04.1, and being at the login screen, before having logged into any user, the SIM-PIN menu appears. I key in the SIM-PIN, hit the button, then I am asked again for the SIM-PIN, this time with the error message "PolicyKit authorization failed: challenge needed for org.freedesktop.ModemManager1.Device.Control". My workaround: Hit the button After that, I am able to log in and connect with my Aldi/Medion Huawei E173 USB stick to the network, if I am an AdminUser. For a user without Admin-rights it is a little bit more complicated after having logged in: he has to unlock the SIM pin again, then he is asked for the Admin passwort because necessary administrative rights. He has to hit twice, but then he can connect to the network without any knowledge of the Admin-paswort. Strange! Will Ubuntu 16.04 sometime come to the point of enabling mobile networking as simple as it was with Ubuntu 14.04? Thank you, siggi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1650792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Re: USB Modem not displayed in network manager
It seems that both ModemManager and NetworkManager are doing the right thing 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) If you're able to reproduce the issue, could you please enable debug logs in both NetworkManager and ModemManager? Please do the following (I know, it's a bit long, sorry for that) $ sudo systemctl stop NetworkManager $ sudo systemctl stop ModemManager $ sudo NetworkManager --log-level=DEBUG --debug | tee $HOME/network- manager.logs then open a new shell and run: $ sudo ModemManager -d | tee $HOME/modem-manager.logs and then attach the two log file in your home directory -- 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/1686573 Title: USB Modem not displayed in network manager Status in modemmanager package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in plasma-nm package in Ubuntu: New Bug description: 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]: [
[Desktop-packages] [Bug 1567796] Re: It is sometimes unable to find DELL WWAN module.
Hi, I'm the author of the patch above, just to note that while in Yakkety the package seems to contain the same bug (at least according to the diff from 1.4.12-1ubuntu2 (in Ubuntu) to 1.6.0-1), the fix is included in ModemManager 1.6.4 which has been released in Zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1567796 Title: It is sometimes unable to find DELL WWAN module. Status in OEM Priority Project: Incomplete Status in modemmanager package in Ubuntu: New Bug description: I have a DELL WWAN module (DW5580) on my platform. Normally it could be detect and used in Ubuntu 16.04 daily image. However it is sometimes unusable and can not be detected. After debugging, we found there is an upstream patch that can fix the issue: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2 Please merge the fix to modem manager to fix the issue. Ubuntu Xenial (daily image) Release: 16.04 modemmanager: Installed: 1.4.12-1ubuntu1 Candidate: 1.4.12-1ubuntu1 Version table: *** 1.4.12-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1567796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1676829] Re: Mic input volume always resets (to middle/low value) on resume or restart
Same thing happens to me everytime I am on a conference call on any videochat app on/off any browser. Hopefully this get patched soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1676829 Title: Mic input volume always resets (to middle/low value) on resume or restart Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sound card: CA0106/CA0111 Each time I start PC - mic input volume resets to some "default" value. This happens from 16.04 (maybe earlier). Now I have 17.04, still have it. Each time I run: 1) alsamixer 2) select input device, "Line In" 3) set it to max. (Or same actions in Ubuntu GUI) Then (after restart or suspend) the volume goes back to some middle value (low for me). I'm pissed off setting it back again and again. Does someone else have this problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1676829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install
It works for me updating libappstreamqt1 to 0.9.4-1ubuntu3 on Xenial 16.04.2. Can someone else confirm, please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1663695 Title: Kubuntu 16.04.1 discover empty after fresh install Status in appstream package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Invalid Status in plasma-discover package in Ubuntu: Invalid Status in appstream source package in Xenial: Fix Committed Status in packagekit source package in Xenial: Invalid Status in plasma-discover source package in Xenial: Invalid Bug description: [Impact] * A previous update made AppStream use modern-style component-ids, thereby breaking the Qt library if it is reading data from the cache and if that data happens to be a desktop-application. * This leads to KDE's Discover not displaying applications. * The issue was introduced by a patch to the Xenial version of AppStream, and is not present in any other version of the package in Ubuntu, affecting Xenial only. [Test Case 1] * Update the libappstream-qt package, run Discover: All apps should be loaded correctly. [Regression Potential] * Low, this change affects only the Qt bindings and nothing else. The change is also a simple string value change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1663695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install
All packages are marked as "technical" and therefore are hidden from the
list in Discover. That's because libAppstreamQt looks for type "desktop"
where instead it is "desktop-application" in the metadata.
** Patch added: "change type string from "desktop" to "desktop-application""
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1663695/+attachment/4848160/+files/appstream_0.9.4-1ubuntu3.debdiff
** Also affects: appstream (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1663695
Title:
Kubuntu 16.04.1 discover empty after fresh install
Status in appstream package in Ubuntu:
New
Status in packagekit package in Ubuntu:
Incomplete
Status in plasma-discover package in Ubuntu:
Invalid
Bug description:
Also reported at (https://github.com/hughsie/PackageKit/issues/177)
I tried discover just after installing Kubuntu 16.04.1 LTS, and some software
was being displayed, but search was not working. I tried to install muon, and
did some software update (which seemed to work fine), and after that discover
would not display any software at all. Updates still work. Muon works fine,
except that search stops working after a while.
There are display issues on top of that, but that is not the worst problem.
Having the default software used for installing software on Kubuntu fail
completely is a rather big issue...
I tried uninstalling plasma-discover and muon, purging them, and reinstalling
them, but that did not change anything. The current version is plasma-discover
5.6.2.
Is there anything I can do to work around the bug ?
This is the output I get when starting it from the CLI:
log_attica_plugin: Loaded paths from config:
(QUrl("http://download.kde.org/ocs/providers.xml";))
knewstuff: Initializing KNS3::Engine from ' "/etc/xdg/comic.knsrc" '
knewstuff: Loading KNewStuff3 config: "/etc/xdg/comic.knsrc"
knewstuff: Categories: ("Plasma Comic")
knewstuff: Using registry file:
"/home/damien/.local/share/knewstuff3/.knsregistry"
knewstuff: Loading KNS2 registry of files for the component: ""
knewstuff: Cache read... entries: 0
knewstuff: loading providers from "http://download.kde.org/ocs/providers.xml";
knewstuff: XmlLoader::load(): url:
QUrl("http://download.kde.org/ocs/providers.xml";)
log_attica_plugin: Loaded paths from config:
(QUrl("http://download.kde.org/ocs/providers.xml";))
knewstuff: Initializing KNS3::Engine from ' "/etc/xdg/plasmoids.knsrc" '
knewstuff: Loading KNewStuff3 config: "/etc/xdg/plasmoids.knsrc"
knewstuff: Categories: ("Plasma 5 Plasmoid")
knewstuff: Loading KNS2 registry of files for the component: ""
knewstuff: Cache read... entries: 0
knewstuff: loading providers from "http://download.kde.org/ocs/providers.xml";
knewstuff: XmlLoader::load(): url:
QUrl("http://download.kde.org/ocs/providers.xml";)
log_attica_plugin: Loaded paths from config:
(QUrl("http://download.kde.org/ocs/providers.xml";))
no providers for "/etc/xdg/comic.knsrc"
invalid kns backend!
no providers for "/etc/xdg/plasmoids.knsrc"
invalid kns backend!
knewstuff: XmlLoader::slotJobData()
knewstuff: XmlLoader::slotJobData()
knewstuff: --Xml Loader-START--
knewstuff: "\n\napi.kde-look.org\n
https://api.kde-look.org/ocs/v1/\n
api.kde-look.org\n\n
https://api.kde-look.org/theme/flatui/img/new/O-standard-logo.png\n
\n
https://api.kde-look.org/content/terms\n
https://api.kde-look.org/register\n\n
\n\n\n\n\n"
knewstuff: --Xml Loader-END--
knewstuff: slotProvidersLoaded
knewstuff: Provider attributes: ""
log_attica_plugin: No credentials found
knewstuff: Engine addProvider called with provider with id
"https://api.kde-look.org/ocs/v1/";
knewstuff: XmlLoader::slotJobData()
knewstuff: XmlLoader::slotJobData()
knewstuff: --Xml Loader-START--
knewstuff: "\n\napi.kde-look.org\n
https://api.kde-look.org/ocs/v1/\n
api.kde-look.org\n\n
https://api.kde-look.org/theme/flatui/img/new/O-standard-logo.png\n
\n
https://api.kde-look.org/content/terms\n
https://api.kde-look.org/register\n\n
\n\n\n\n\n"
knewstuff: --Xml Loader-END--
knewstuff: slotProvidersLoaded
knewstuff: Provider attributes: ""
log_attica_plugin: No credentials found
knewstuff: Engine addProvider called with provider with id
"https://api.kde-look.org/ocs/v1/";
knewstuff: providerInitialized "api.kde-look.org"
knewstuff: providers loaded
knewstuff: providerInitialized "api.kde-look.org"
knewstuff: providers loaded
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: plasma-discover 5.6.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-62.83-ge
[Desktop-packages] [Bug 1503310] Re: window content doesn't refresh, only if window is moved
I'm using NVIDIA driver 367.57, kernel 4.4.0-64-generic and did NOT have this
issue
prior to xenial (although, I think I made a huge leap when upgrading, I might
have
skipped 14.x).
--
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/1503310
Title:
window content doesn't refresh, only if window is moved
Status in compiz package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
Confirmed
Bug description:
I suppose this is a bug with the nvidia driver, but I'm not sure.
After the second-to-last routine software update (which I think
updated the nvidia driver), changing window content is only refreshed
if the window is moved.
Ubuntu 12.04.5 LTS, kernel 3.2.0-91-generic,
NVidia driver installed: 340.93-0ubuntu0.0.0.1,
Thinkpad laptop with nvidia graphics card (see below),
Window manager: Gnome Classic
How to reproduce the bug: Log in under Gnome Classic. Open Gnome
terminal. Execute some command (ls). Open new tab in terminal. Execute
some other command (ps), just to have different tab contents. Switch
back and forth between the tabs using the mouse. After some switches,
neither the tab rider is activated nor the tab content is refreshed
any longer. Only if you move the window, the tab rider gets activated
and the tab content is refreshed. The same problem occurs in other
applications (e.g. in thunderbird when selecting an email --- email
list entry is not marked and email content is not shown, only if you
move the window), so it is not application-specific.
The bug disappears when using the window manager "Gnome Classic (no
effects)" instead (which is "non-compositing" in contrast to "Gnome
Classic"). The bug is also present in other window magagers
("Ubuntu").
Side remark: I tried but failed to switch back to an earlier version
of the nvidia driver (from 340 to 331) using synaptic: When
deinstalling 340 and installing 331 instead, synaptic complains that
it depends on 340. So I can only guess that the bug is caused by the
nvidia driver.
Any help would be highly appreciated as the bug is really annoying.
% nvidia-smi
Tue Oct 6 16:13:30 2015
+--+
| NVIDIA-SMI 340.93 Driver Version: 340.93 |
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC
|
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M.
|
|===+==+==|
| 0 NVS 5400M Off | :01:00.0 N/A | N/A
|
| N/A 44CP8N/A / N/A |194MiB / 1023MiB | N/A Default
|
+---+--+--+
+-+
| Compute processes: GPU Memory
|
| GPU PID Process name Usage
|
|=|
|0Not Supported
|
+-+
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nvidia-340 340.93-0ubuntu0.0.0.1
ProcVersionSignature: Ubuntu 3.2.0-91.129-generic 3.2.71
Uname: Linux 3.2.0-91-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.11
Architecture: amd64
Date: Tue Oct 6 16:10:32 2015
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/tcsh
SourcePackage: nvidia-graphics-drivers-340
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1503310/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1503310] Re: window content doesn't refresh, only if window is moved
I'm having an issue very much like this one: repainting of certain
windows just stop. Input, menu's, mouse everything still works fine -
it's just the repainting of the window that stops. Only way to recover
is to close the window and restart the application.
However, I am using 16.04 ...
Does anyone have suggestions on what I can try to investigate this?
Is there another bug report for this somewhere at the moment?
--
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/1503310
Title:
window content doesn't refresh, only if window is moved
Status in compiz package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
Confirmed
Bug description:
I suppose this is a bug with the nvidia driver, but I'm not sure.
After the second-to-last routine software update (which I think
updated the nvidia driver), changing window content is only refreshed
if the window is moved.
Ubuntu 12.04.5 LTS, kernel 3.2.0-91-generic,
NVidia driver installed: 340.93-0ubuntu0.0.0.1,
Thinkpad laptop with nvidia graphics card (see below),
Window manager: Gnome Classic
How to reproduce the bug: Log in under Gnome Classic. Open Gnome
terminal. Execute some command (ls). Open new tab in terminal. Execute
some other command (ps), just to have different tab contents. Switch
back and forth between the tabs using the mouse. After some switches,
neither the tab rider is activated nor the tab content is refreshed
any longer. Only if you move the window, the tab rider gets activated
and the tab content is refreshed. The same problem occurs in other
applications (e.g. in thunderbird when selecting an email --- email
list entry is not marked and email content is not shown, only if you
move the window), so it is not application-specific.
The bug disappears when using the window manager "Gnome Classic (no
effects)" instead (which is "non-compositing" in contrast to "Gnome
Classic"). The bug is also present in other window magagers
("Ubuntu").
Side remark: I tried but failed to switch back to an earlier version
of the nvidia driver (from 340 to 331) using synaptic: When
deinstalling 340 and installing 331 instead, synaptic complains that
it depends on 340. So I can only guess that the bug is caused by the
nvidia driver.
Any help would be highly appreciated as the bug is really annoying.
% nvidia-smi
Tue Oct 6 16:13:30 2015
+--+
| NVIDIA-SMI 340.93 Driver Version: 340.93 |
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC
|
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M.
|
|===+==+==|
| 0 NVS 5400M Off | :01:00.0 N/A | N/A
|
| N/A 44CP8N/A / N/A |194MiB / 1023MiB | N/A Default
|
+---+--+--+
+-+
| Compute processes: GPU Memory
|
| GPU PID Process name Usage
|
|=|
|0Not Supported
|
+-+
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nvidia-340 340.93-0ubuntu0.0.0.1
ProcVersionSignature: Ubuntu 3.2.0-91.129-generic 3.2.71
Uname: Linux 3.2.0-91-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.11
Architecture: amd64
Date: Tue Oct 6 16:10:32 2015
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=C
SHELL=/bin/tcsh
SourcePackage: nvidia-graphics-drivers-340
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1503310/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1662836] [NEW] repeatedly turning BT off and off crashes gnome
Public bug reported: A bit of background (not sure if important): in our setup RFKill is driving a GPIO to enable / disable the BT transceiver. This is a slow operation and it could take ~500ms for the RFKill subsystem to complete the operation. In the Bluetooth configuration panel if I click on the Bluetooth on/off toggle switch 5+ times in a row repeatedly, gnome (or BT configuration panel) crashes. This is what I have in the journal: ``` gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_complete_in_idle: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_complete_in_idle: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_complete_in_idle: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed kernel: BT_RADIO going: on kernel: BCM_BT: going ON gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_complete_in_idle: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: Failed to set RFKill: Stream has outstanding operation gnome-settings-daemon.desktop[886]: ** gnome-settings-daemon.desktop[886]: rfkill-plugin:ERROR:rfkill-glib.c:168:write_change_all_timeout_cb: assertion failed: (rfkill->priv->event) ``` Coredump: ``` Core was generated by `/usr/lib/gnome-settings-daemon/gnome-settings-daemon'. Program terminated with signal SIGABRT, Aborted. #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 44 ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44 #1 0xf687bee6 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xf687cbee in __GI_abort () at abort.c:89 #3 0xf69bc7ea in g_assertion_message () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 #4 0xf69bc888 in g_assertion_message_expr () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 #5 0xf285d562 in write_change_all_timeout_cb (rfkill=0x643430, rfkill@entry=0x4b3f70) at rfkill-glib.c:168 #6 0xf285dc68 in cc_rfkill_glib_send_change_all_event (rfkill=0x4b3f70, rfkill_type=2, enable=0, cancellable=0xf285e0b8, callback=0xf285c709 , user_data=0x492b90) at rfkill-glib.c:242 #7 0xf285cf78 in engine_set_bluetooth_airplane_mode (enable=, manager=0x492b90) at gsd-rfkill-manager.c:345 #8 handle_set_property (connection=, sender=, object_path=, interface_name=, property_name=0xf490f528 "BluetoothAirplaneMode", value=0xf4919460, error=0xffc75dac, user_data=0x492b90) at gsd-rfkill-manager.c:395 #9 0xf6b162ea in ?? () from /lib/arm-linux-gnueabihf/libgio-2.0.so.0 ``` At least for `assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed` what I think it's happening here is that `cc_rfkill_glib_send_change_all_event()` is rapidly called and several request for the asynchronous writing are queued on several `GSimpleAsyncResult` objects. When the first writing is done in `write_change_all_done_cb()` the latest `rfkill->priv->simple` object is freed. All the subsequent `write_change_all_done_cb()` callbacks find a NULL `rfkill->priv->simple`. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Description changed: A bit of background (not sure if important): in our setup RFKill is driving a GPIO to enable / disable the BT transceiver. This is a slow operation and it could take ~500ms for the RFKill subsystem to complete the operation. In the Bluetooth configuration panel if I click on the Bluetooth on/off toggle switch 5+ times in a row repeatedly, gnome (or BT configuration panel) crashes. This is what I have in the journal: ``` gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_complete_in_idle: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_complete_in_idle: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed gnome-settings-[886]: g_simple_async_result_complete_in_idle: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed kernel: BT_RADIO going: on kernel: BCM_BT: going ON gnome-settings-[886]: g_simple_async_result_take_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (si
[Desktop-packages] [Bug 1654458] Re: default trusty g++ compiler gives warnings about deprecated use of std::auto_ptr in this package.
@Murray Thank you for your comment. I could not find any package for ubuntu that has this fixed. As it is an ABI breakage, as I understand, any project that wants to use C++11 standard (let alone C++17) will want to immediately start to demand and link with the new libxml++; so it's a problem that there isn't a package in ubuntu for that in 2017. Or am I missing something? ** Summary changed: - default trusty g++ compiler gives warnings about deprecated use of std::auto_ptr in this package. + default xenial g++ compiler gives warnings about deprecated use of std::auto_ptr in this package. ** Description changed: - Default trusty install leaves me with a flood of the following when + Default xenial install leaves me with a flood of the following when trying to compile my application, using libxml++2.6: In file included from /usr/include/libxml++-2.6/libxml++/libxml++.h:54:0, [...snip...] /usr/include/libxml++-2.6/libxml++/parsers/textreader.h:260:10: warning: ‘template class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] - std::auto_ptr propertyreader; + std::auto_ptr propertyreader; as well as similar warnings about std::auto_ptr elsewhere in libxml++ headers. The work around is to ignore the warnings or turn them off, but that is not what I should have to do (I need to have warnings turned on, as a developer). Regards, Carlo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libxml++2.6-dev 2.40.1-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jan 6 02:44:54 2017 InstallationDate: Installed on 2016-01-11 (360 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libxml++2.6 UpgradeStatus: Upgraded to xenial on 2016-10-29 (68 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml++2.6 in Ubuntu. https://bugs.launchpad.net/bugs/1654458 Title: default xenial g++ compiler gives warnings about deprecated use of std::auto_ptr in this package. Status in libxml++2.6 package in Ubuntu: New Bug description: Default xenial install leaves me with a flood of the following when trying to compile my application, using libxml++2.6: In file included from /usr/include/libxml++-2.6/libxml++/libxml++.h:54:0, [...snip...] /usr/include/libxml++-2.6/libxml++/parsers/textreader.h:260:10: warning: ‘template class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] std::auto_ptr propertyreader; as well as similar warnings about std::auto_ptr elsewhere in libxml++ headers. The work around is to ignore the warnings or turn them off, but that is not what I should have to do (I need to have warnings turned on, as a developer). Regards, Carlo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libxml++2.6-dev 2.40.1-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jan 6 02:44:54 2017 InstallationDate: Installed on 2016-01-11 (360 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libxml++2.6 UpgradeStatus: Upgraded to xenial on 2016-10-29 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml++2.6/+bug/1654458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654458] [NEW] default trusty g++ compiler gives warnings about deprecated use of std::auto_ptr in this package.
Public bug reported: Default trusty install leaves me with a flood of the following when trying to compile my application, using libxml++2.6: In file included from /usr/include/libxml++-2.6/libxml++/libxml++.h:54:0, [...snip...] /usr/include/libxml++-2.6/libxml++/parsers/textreader.h:260:10: warning: ‘template class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] std::auto_ptr propertyreader; as well as similar warnings about std::auto_ptr elsewhere in libxml++ headers. The work around is to ignore the warnings or turn them off, but that is not what I should have to do (I need to have warnings turned on, as a developer). Regards, Carlo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libxml++2.6-dev 2.40.1-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jan 6 02:44:54 2017 InstallationDate: Installed on 2016-01-11 (360 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libxml++2.6 UpgradeStatus: Upgraded to xenial on 2016-10-29 (68 days ago) ** Affects: libxml++2.6 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml++2.6 in Ubuntu. https://bugs.launchpad.net/bugs/1654458 Title: default trusty g++ compiler gives warnings about deprecated use of std::auto_ptr in this package. Status in libxml++2.6 package in Ubuntu: New Bug description: Default trusty install leaves me with a flood of the following when trying to compile my application, using libxml++2.6: In file included from /usr/include/libxml++-2.6/libxml++/libxml++.h:54:0, [...snip...] /usr/include/libxml++-2.6/libxml++/parsers/textreader.h:260:10: warning: ‘template class std::auto_ptr’ is deprecated [-Wdeprecated-declarations] std::auto_ptr propertyreader; as well as similar warnings about std::auto_ptr elsewhere in libxml++ headers. The work around is to ignore the warnings or turn them off, but that is not what I should have to do (I need to have warnings turned on, as a developer). Regards, Carlo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libxml++2.6-dev 2.40.1-1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jan 6 02:44:54 2017 InstallationDate: Installed on 2016-01-11 (360 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: libxml++2.6 UpgradeStatus: Upgraded to xenial on 2016-10-29 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml++2.6/+bug/1654458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Not stand it anymore this gnome network managers. Buggy, Buggy. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Can anyone recommend a workaround for Elementary OS? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Fix Committed Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1598978] Re: No Notification For Repeat Google Authenticator Attempts
The default gtk greeter. I can attach config files if necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1598978 Title: No Notification For Repeat Google Authenticator Attempts Status in lightdm package in Ubuntu: Incomplete Bug description: Not using Ubuntu, but Arch Linux. Lightdm version 1.18.2. I have enabled 2fa using google authentication (pam_google_authenticator.so enabled in pam). The first time works great; I enter my password and then a small banner pops up saying "Authentication Code". But say I enter my password incorrectly (which doesn't get checked until the authentication code is good) the second time I have to enter the authentication code there is no banner. Obviously not critical, but it does make it sometimes tough to remember if this is an authentication code entry or a regular password entry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1598978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1598978] [NEW] No Notification For Repeat Google Authenticator Attempts
Public bug reported: Not using Ubuntu, but Arch Linux. Lightdm version 1.18.2. I have enabled 2fa using google authentication (pam_google_authenticator.so enabled in pam). The first time works great; I enter my password and then a small banner pops up saying "Authentication Code". But say I enter my password incorrectly (which doesn't get checked until the authentication code is good) the second time I have to enter the authentication code there is no banner. Obviously not critical, but it does make it sometimes tough to remember if this is an authentication code entry or a regular password entry. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1598978 Title: No Notification For Repeat Google Authenticator Attempts Status in lightdm package in Ubuntu: New Bug description: Not using Ubuntu, but Arch Linux. Lightdm version 1.18.2. I have enabled 2fa using google authentication (pam_google_authenticator.so enabled in pam). The first time works great; I enter my password and then a small banner pops up saying "Authentication Code". But say I enter my password incorrectly (which doesn't get checked until the authentication code is good) the second time I have to enter the authentication code there is no banner. Obviously not critical, but it does make it sometimes tough to remember if this is an authentication code entry or a regular password entry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1598978/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1253002] Re: Xorg crash when using Chrome
in my case, I guess that the problem starts when I open html/php pages within javascript code malformed or bad written. Could be a javascript code which has something to deal with GPU and consequently crash Xorg ?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1253002 Title: Xorg crash when using Chrome Status in Linux Mint: New Status in xorg-server package in Ubuntu: New Bug description: I've just upgraded to Linux Mint 16 "Petra" Cinnamon 64bit and was using it for about an hour and then suddenly while browsing with Chrome the Xorg crashed and it restarted - I was back on the login screen. I've tried two more times to use Chrome and the crash happened again and again. Chrome is 31.0.1650.57 Attached crash report. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1253002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458351] Re: Some Fn+ Keys Not Working
After fresh install of 15.04 the problem persists. Seems to be same result for acpi_listen with no output appearing. Volume buttons and others still functional but no brightness function keys. -- 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/1458351 Title: Some Fn+ Keys Not Working Status in xorg package in Ubuntu: Incomplete Bug description: Brightness control keys on my laptop not being recognized (including no output from acpi_listen). Running Ubuntu 14.04.2 LTS. Other function keys do work and are recognized ex. volume. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 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: Sun May 24 12:59:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:181d] InstallationDate: Installed on 2015-05-23 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed root=UUID=246981b4-9b06-41f9-ac18-1e5ba27d4247 ro quiet splash acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA 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.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun May 24 12:07:13 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8493 vendor AUO xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1458351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458351] [NEW] Some Fn+ Keys Not Working
Public bug reported: Brightness control keys on my laptop not being recognized (including no output from acpi_listen). Running Ubuntu 14.04.2 LTS. Other function keys do work and are recognized ex. volume. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 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: Sun May 24 12:59:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:181d] InstallationDate: Installed on 2015-05-23 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed root=UUID=246981b4-9b06-41f9-ac18-1e5ba27d4247 ro quiet splash acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA 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.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun May 24 12:07:13 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8493 vendor AUO xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1458351 Title: Some Fn+ Keys Not Working Status in xorg package in Ubuntu: New Bug description: Brightness control keys on my laptop not being recognized (including no output from acpi_listen). Running Ubuntu 14.04.2 LTS. Other function keys do work and are recognized ex. volume. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 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: Sun May 24 12:59:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:181d] InstallationDate: Installed on 2015-05-23 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
[Desktop-packages] [Bug 1010349] Re: Evolution address book inaccessible without killing one time "e-addressbook-factory"
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1010349 Title: Evolution address book inaccessible without killing one time "e -addressbook-factory" Status in evolution-data-server package in Ubuntu: Confirmed Bug description: After a fresh boot of my system, Evolution is not able to access my work address book on LDAP and my personnal address book on Google. With Google address book I get the error "Cannot open book: Source already loaded!" After shutting down Evolution and killing by hand : /usr/lib/evolution/e-addressbook-factory. I relaunch Evolution and everything go right. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution-data-server 3.2.3-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jun 8 09:07:18 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1010349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1427700] Re: Nautilus icon in launcher creates seperate icon when clicked
Fixed the bug of double icon, but now there's not the quick list. -- 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/1427700 Title: Nautilus icon in launcher creates seperate icon when clicked Status in bamf package in Ubuntu: Fix Released Bug description: Sometimes clicking the Nautilus icon in the launcher opens Nautilus with a seperate additional Nautilus icon in the launcher below the original 'locked' icon. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 3 14:18:52 2015 InstallationDate: Installed on 2015-03-03 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150303) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1427700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1410567] [NEW] nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build
Public bug reported: I am not able to write any technician issue here, but I THINK when I installed Ubuntu 14.14 and then I followed some external instructions as "10 things to do after installing Ubuntu 14.10" there was something not proper. 1. Since then VLC did not work. I unsinstalled VLC via Ubuntu software Centre but I am not anymore able to install it due conflicts in already installed files. 2. JDownloader tells me always it does not like the version of Java I Installed. 3. RhythmBox does not read .ape and .mcp files anymore (I think this is connected with VLC becase of codecs). It maybe I wrote down some really stupid things here but this is my best (you can imagine my worst...). ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Mon Jan 12 22:58:02 2015 PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-30 (74 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1410567 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: I am not able to write any technician issue here, but I THINK when I installed Ubuntu 14.14 and then I followed some external instructions as "10 things to do after installing Ubuntu 14.10" there was something not proper. 1. Since then VLC did not work. I unsinstalled VLC via Ubuntu software Centre but I am not anymore able to install it due conflicts in already installed files. 2. JDownloader tells me always it does not like the version of Java I Installed. 3. RhythmBox does not read .ape and .mcp files anymore (I think this is connected with VLC becase of codecs). It maybe I wrote down some really stupid things here but this is my best (you can imagine my worst...). ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Mon Jan 12 22:58:02 2015 PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-30 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1410567/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1410562] [NEW] nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build
Public bug reported: I am not able to write any technician issue here ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Mon Jan 12 22:58:02 2015 PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-30 (74 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1410562 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: I am not able to write any technician issue here ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Mon Jan 12 22:58:02 2015 PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-30 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1410562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1402059] Re: Small gap appears in Firefox main window after first use of globalmenu
** Description changed:
To reproduce:
1. Start Firefox on Unity
2. Open any menu from the globalmenu (e.g. File) of main window
3. Notice that the toolbars have moved 2px below their original position (see
attachment)
This seems to happen only on the main window, other windows such as the
- Scratchpad window doesn't show the problem.
+ Scratchpad window don't show the problem.
I added to my userChrome.css the following piece of code:
window[shellshowingmenubar="true"]
toolbar[type="menubar"]:not([customizing="true"]){
height: 0 !important;
}
That solved the problem for me, and so far I didn't found anything
broken by that CSS rule. So it should be enough to put it in xul.css by
unity-menubar.patch.
--
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/1402059
Title:
Small gap appears in Firefox main window after first use of globalmenu
Status in firefox package in Ubuntu:
New
Bug description:
To reproduce:
1. Start Firefox on Unity
2. Open any menu from the globalmenu (e.g. File) of main window
3. Notice that the toolbars have moved 2px below their original position (see
attachment)
This seems to happen only on the main window, other windows such as
the Scratchpad window don't show the problem.
I added to my userChrome.css the following piece of code:
window[shellshowingmenubar="true"]
toolbar[type="menubar"]:not([customizing="true"]){
height: 0 !important;
}
That solved the problem for me, and so far I didn't found anything
broken by that CSS rule. So it should be enough to put it in xul.css
by unity-menubar.patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1402059/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1402059] [NEW] Small gap appears in Firefox main window after first use of globalmenu
Public bug reported:
To reproduce:
1. Start Firefox on Unity
2. Open any menu from the globalmenu (e.g. File) of main window
3. Notice that the toolbars have moved 2px below their original position (see
attachment)
This seems to happen only on the main window, other windows such as the
Scratchpad window doesn't show the problem.
I added to my userChrome.css the following piece of code:
window[shellshowingmenubar="true"]
toolbar[type="menubar"]:not([customizing="true"]){
height: 0 !important;
}
That solved the problem for me, and so far I didn't found anything
broken by that CSS rule. So it should be enough to put it in xul.css by
unity-menubar.patch.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "screenshot.png"
https://bugs.launchpad.net/bugs/1402059/+attachment/4279889/+files/screenshot.png
** Description changed:
To reproduce:
1. Start Firefox on Unity
2. Open any menu from the globalmenu (e.g. File) of main window
3. Notice that the toolbars have moved 2px below their original position (see
attachment)
This seems to happen only on the main window, other windows such as the
Scratchpad window doesn't show the problem.
I added to my userChrome.css the following piece of code:
window[shellshowingmenubar="true"]
toolbar[type="menubar"]:not([customizing="true"]){
- height: 0 !important;
+ height: 0 !important;
}
That solved the problem for me, and so far I didn't found anything
- broken by that CSS rule. So it should be enough to put it xul.css by
+ broken by that CSS rule. So it should be enough to put it in xul.css by
unity-menubar.patch.
--
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/1402059
Title:
Small gap appears in Firefox main window after first use of globalmenu
Status in firefox package in Ubuntu:
New
Bug description:
To reproduce:
1. Start Firefox on Unity
2. Open any menu from the globalmenu (e.g. File) of main window
3. Notice that the toolbars have moved 2px below their original position (see
attachment)
This seems to happen only on the main window, other windows such as
the Scratchpad window doesn't show the problem.
I added to my userChrome.css the following piece of code:
window[shellshowingmenubar="true"]
toolbar[type="menubar"]:not([customizing="true"]){
height: 0 !important;
}
That solved the problem for me, and so far I didn't found anything
broken by that CSS rule. So it should be enough to put it in xul.css
by unity-menubar.patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1402059/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1380042] Re: Chromium refreshes the pages upon network connect with no way to stop it
Hi, Can you tell us also the list of your chromium extensions which you have installed ? It could be an extension, the cause, maybe. -- 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/1380042 Title: Chromium refreshes the pages upon network connect with no way to stop it Status in “chromium-browser” package in Ubuntu: New Bug description: FOR SECURITY IMPLICATION SEE &&& My (and many people's that i know) workflow: 1. Open the page that you intend to read/process/comment on/etc in a new tab 2. Leave the tab open until the desired action is done (this results in many open tabs, some of which are youtube videos and such). 3. Before the reboot do not close the browser, but allow it to be shut down due to computer shutdown. 4. After the reboot, but before connecting the network open the browser and tell it to reopen the tabs. 5. Connect to the network and refresh the tabs that are needed for work. What happens: After upgrading from 13.10 to 14.04 all the tabs refresh themselves without being told to as soon as i connect to the network. There seems to be no way to stop this behaviour. I end up racing with "Ctrl+Tab - Esc - Ctrl+Tab - Esc" combination through my tabs to end the reload process. A lot of unneeded at this time tabs take up computer resources due to flash and other multimedia content. At one time my computer woke me at three in the morning, because my internet was down in the evening and just came on at night, so Chromium has restarted all the youtube videos for me. &&& In addition to that there is a security issue that i have no time to load VPN before such loading begins. This makes the traffic that is assumed to be secure to begin through an unsecure channel. &&& What i expect to happen: No browser should load anything unless it is asked by the user to do so, and not any earlier. Chromium should load the pages in three cases: 1) When the tab is opened. 2) When the reload is pressed. 3) Then javascript causes page reload, but only after the page was already loaded and JS began to run ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.14.04.1~pkg1049 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 11 13:02:58 2014 InstallationDate: Installed on 2014-10-02 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-10-03T10:31:27.498350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1380042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1367870] Re: Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially when using Google Chrome
After the update of Google Chrome to version 38.0.2125.101, everytime I watch a video on youtube, after few time, the screen becomes black as freezed and after other seconds ubuntu goes in crash completly then I must reboot the pc manually. I have ubuntu 14.04 with intel graphic card integrated. I also tried to disable the Acceleration hardware in chrome://flags, but the problem is always the same. I guess it could be a problem of Google Chrome rather than of Xorg which is quite stable. I hope that someone can fix this bug soon. With the previous version of Chrome, I didn't have this problem. This bug report is like to Bug #1369222 (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1369222) -- 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/1367870 Title: Ubuntu 14.04 system with Radeon HD 6330M hangs regularly, especially when using Google Chrome Status in “xorg” package in Ubuntu: New Bug description: I'm reporting this bug at the request of k...@chromium.org at https://code.google.com/p/chromium/issues/detail?id=404357#c34 . Please see https://code.google.com/p/chromium/issues/detail?id=404357 for details. The appropriate package for this bug might be xserver- xorg-video-ati but that's a guess. Summary: Using Google Chrome 36+ on an ubuntu 14.04 system with an AMD Radeon HD 6330M graphics card has been regularly causing system hangs. These appear to be particularly likely when playing Flash-based games such as those on Facebook. Scroll up and down using the vertical scrollbar or the mousewheel and chrome will segfault. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 10 19:29:10 2014 DistUpgraded: 2014-07-06 18:19:11,036 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Robson LE [Radeon HD 6330M] [1002:68e5] (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Cedar [Radeon HD 5450] [148c:5450] InstallationDate: Installed on 2013-10-19 (326 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: MEDIONPC MS-7366 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=57c8f83f-22f9-4998-9943-259a1df235a0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-07-06 (66 days ago) XorgConf: Section "Module" Load"glx" EndSection dmi.bios.date: 01/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7366NM7.20E dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7366 dmi.board.vendor: MEDIONPC dmi.board.version: 2.2 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.:bvrA7366NM7.20E:bd01/08/2008:svnMEDIONPC:pnMS-7366:pvr2.2:rvnMEDIONPC:rnMS-7366:rvr2.2:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7366 dmi.product.version: 2.2 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Sep 10 19:00:35 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1367870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launch
[Desktop-packages] [Bug 1369222] Re: xorg random crash
After the update of Google Chrome to version 38.0.2125.101, everytime I watch a video on youtube, after few time, the screen becomes black as freezed and after other seconds ubuntu goes in crash completly then I must reboot the pc manually. I also tried to disable the Acceleration hardware in chrome://flags, but the problem is always the same. I guess it could be a problem of Google Chrome rather than of Xorg which is quite stable. I hope that someone can fix this bug soon. With the previous version of Chrome, I didn't have this problem. Thanks. -- 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/1369222 Title: xorg random crash Status in “xorg” package in Ubuntu: New Bug description: I was just watching a youtube video fullscreen in Google Chrome. I exited fullscreen with the Esc key: starting from that moment, the whole Google Chrome window's content was replaced by a frozen frame of the video (I could still hear the audio streaming). I couldn't see the other tabs. After a few seconds, Xorg crashed. I already sent the automatical crash report (the window that pops up telling you there was an "internal problem") but that doesn't give me any reference to the bug report, it doesn't even tell me if the report was sent succesfully. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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: Sun Sep 14 09:20:58 2014 DistUpgraded: 2014-05-24 19:43:23,984 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-10-11 (337 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-24 (112 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Sep 14 09:19:00 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1369222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1323618] [NEW] Pymol not working.
Public bug reported: I give the sudo apt-get install pymol, but when i try to run it typing pymol it gives this error: X Error of failed request: GLXBadContext Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 40 Current serial number in output stream: 39 PyMOL: abrupt program termination. Can anybody help pls? By the way : Version: Description:Ubuntu 12.04.4 LTS Release:12.04 Pymol: Installed: 1.4.1-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Description changed: I give the sudo apt-get install pymol, but when i try to run it typing pymol it gives this error: X Error of failed request: GLXBadContext - Major opcode of failed request: 153 (GLX) - Minor opcode of failed request: 6 (X_GLXIsDirect) - Serial number of failed request: 40 - Current serial number in output stream: 39 - PyMOL: abrupt program termination. + Major opcode of failed request: 153 (GLX) + Minor opcode of failed request: 6 (X_GLXIsDirect) + Serial number of failed request: 40 + Current serial number in output stream: 39 + PyMOL: abrupt program termination. Can anybody help pls? + + By the way : + + Version: + Description: Ubuntu 12.04.4 LTS + Release: 12.04 + + Pymol: + Installed: 1.4.1-3 -- 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/1323618 Title: Pymol not working. Status in “xorg” package in Ubuntu: New Bug description: I give the sudo apt-get install pymol, but when i try to run it typing pymol it gives this error: X Error of failed request: GLXBadContext Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 40 Current serial number in output stream: 39 PyMOL: abrupt program termination. Can anybody help pls? By the way : Version: Description: Ubuntu 12.04.4 LTS Release: 12.04 Pymol: Installed: 1.4.1-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1323618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1263519] Re: [7260IT, Realtek ALC880, Line Out, N/A] No sound at all
Dear Raymond, thank you for your assistance. Adding model=3stack solved the problem. Sound is back. Thank you very much. Original message From: Raymond <1263...@bugs.launchpad.net> Date:23/12/2013 14:06 (GMT+01:00) To: careug...@gmail.com Subject: [Bug 1263519] Re: [7260IT, Realtek ALC880, Line Out, N/A] No sound at all 0:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 03) Subsystem: Gateway, Inc. Device [107b:4037] what is the model name of your gateway ? do it support sprig out ? you have to specify model=3stack https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=67b6ec3196da235317ff1b9474f17379b78f3294 send email to the author to add pci quirk -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1263519 Title: [7260IT, Realtek ALC880, Line Out, N/A] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: I just installed Ubuntu 12.04 LTS approaching LINUX for the first time. Everything went okay, I was impressed (network and internet connection auto configure, video board and screen perfectly detected), but sound there is no way I can hear anything. I tried to download drivers from Realteck (LinuxPkg_5.18.tar.bz2), tried to follow the install instructions (I am new to Ubuntu), but actually got thing worse. Worse beacause I had a webcam with microphone correctly configured and now they do not exist anymore on the system. If you have any hint, I would greatly appreciate it. Thank you, ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.2x-130606-v5.18. Compiled on Dec 22 2013 for kernel 3.8.0-35-generic (SMP). AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ceugeni 1733 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x4820 irq 46' Mixer name : 'Realtek ALC880' Components : 'HDA:10ec0880,0860,0009' Controls : 13 Simple ctrls : 5 CurrentDmesg: Date: Sun Dec 22 18:43:42 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio interno - HDA Intel Symptom_DevicesInUse: 1733 ceugeni F pulseaudio PID ACCESS COMMAND Symptom_Jack: Line Out, N/A Symptom_Type: No sound at all Title: [7260IT, Realtek ALC880, Line Out, N/A] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2005 dmi.bios.vendor: Intel Corp. dmi.bios.version: AG91510J.15A.0816.2005.0214.1818 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D915GAG dmi.board.vendor: Intel Corporation dmi.board.version: AAC77881-306 dmi.chassis.type: 3 dmi.chassis.vendor: EMACHINES dmi.modalias: dmi:bvnIntelCorp.:bvrAG91510J.15A.0816.2005.0214.1818:bd02/14/2005:svnEMACHINES:pn7260IT:pvr:rvnIntelCorporation:rnD915GAG:rvrAAC77881-306:cvnEMACHINES:ct3:cvr: dmi.product.name: 7260IT dmi.sys.vendor: EMACHINES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1263519/+subscriptions -- 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/1263519 Title: [7260IT, Realtek ALC880, Line Out, N/A] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: I just installed Ubuntu 12.04 LTS approaching LINUX for the first time. Everything went okay, I was impressed (network and internet connection auto configure, video board and screen perfectly detected), but sound there is no way I can hear anything. I tried to download drivers from Realteck (LinuxPkg_5.18.tar.bz2), tried to follow the install instructions (I am new to Ubuntu), but actually got thing worse. Worse beacause I had a webcam with microphone correctly configured and now they do not exist anymore on the system.
[Desktop-packages] [Bug 1263519] [NEW] [7260IT, Realtek ALC880, Line Out, N/A] No sound at all
Public bug reported:
I just installed Ubuntu 12.04 LTS approaching LINUX for the first time.
Everything went okay, I was impressed (network and internet connection auto
configure, video board and screen perfectly detected), but sound there is no
way I can hear anything.
I tried to download drivers from Realteck (LinuxPkg_5.18.tar.bz2), tried to
follow the install instructions (I am new to Ubuntu), but actually got thing
worse. Worse beacause I had a webcam with microphone correctly configured and
now they do not exist anymore on the system.
If you have any hint, I would greatly appreciate it.
Thank you,
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic i686
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.2x-130606-v5.18.
Compiled on Dec 22 2013 for kernel 3.8.0-35-generic (SMP).
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ceugeni1733 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x4820 irq 46'
Mixer name : 'Realtek ALC880'
Components : 'HDA:10ec0880,0860,0009'
Controls : 13
Simple ctrls : 5
CurrentDmesg:
Date: Sun Dec 22 18:43:42 2013
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386
(20130820.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Audio interno - HDA Intel
Symptom_DevicesInUse:
1733 ceugeni F pulseaudio
PID ACCESS COMMAND
Symptom_Jack: Line Out, N/A
Symptom_Type: No sound at all
Title: [7260IT, Realtek ALC880, Line Out, N/A] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2005
dmi.bios.vendor: Intel Corp.
dmi.bios.version: AG91510J.15A.0816.2005.0214.1818
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D915GAG
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC77881-306
dmi.chassis.type: 3
dmi.chassis.vendor: EMACHINES
dmi.modalias:
dmi:bvnIntelCorp.:bvrAG91510J.15A.0816.2005.0214.1818:bd02/14/2005:svnEMACHINES:pn7260IT:pvr:rvnIntelCorporation:rnD915GAG:rvrAAC77881-306:cvnEMACHINES:ct3:cvr:
dmi.product.name: 7260IT
dmi.sys.vendor: EMACHINES
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise running-unity
--
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/1263519
Title:
[7260IT, Realtek ALC880, Line Out, N/A] No sound at all
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
I just installed Ubuntu 12.04 LTS approaching LINUX for the first time.
Everything went okay, I was impressed (network and internet connection auto
configure, video board and screen perfectly detected), but sound there is no
way I can hear anything.
I tried to download drivers from Realteck (LinuxPkg_5.18.tar.bz2), tried to
follow the install instructions (I am new to Ubuntu), but actually got thing
worse. Worse beacause I had a webcam with microphone correctly configured and
now they do not exist anymore on the system.
If you have any hint, I would greatly appreciate it.
Thank you,
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic i686
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.2x-130606-v5.18.
Compiled on Dec 22 2013 for kernel 3.8.0-35-generic (SMP).
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC880 Analog [ALC880 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ceugeni1733 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x4820 irq 46'
Mixer name : 'Realtek ALC880'
Components : 'HDA:10ec0880,0860,0009'
Controls : 13
Simple ctr
[Desktop-packages] [Bug 1232726] Re: Dash bg color doesn't match its surroundings
Today I upgraded to Ubuntu 14.04 and this bug is no longer present, you can also solve it on 13.10? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1232726 Title: Dash bg color doesn't match its surroundings Status in Unity: Fix Committed Status in Unity 7.1 series: In Progress Status in “mesa” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Saucy: In Progress Bug description: Lately, after login the Dash keeps a black background even if the Launcher and panel follow the current wallpaper color. I've added a screenshot. If I change the wallpaper, Dash recovers its chameleonic effect (until next reboot). Also, this started happening at the same time that a new error message (at log time) appeared, I've attached this error message, too. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 unity: Installed: 7.1.1+13.10.20130927.1-0ubuntu1 Candidate: 7.1.1+13.10.20130927.1-0ubuntu1 Version table: *** 7.1.1+13.10.20130927.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20130927.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Sep 29 08:00:07 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30a2] Subsystem: Hewlett-Packard Company Device [103c:30a2] InstallationDate: Installed on 2013-08-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM) MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68YGU Ver. F.0A dmi.board.name: 30A2 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.17 dmi.chassis.asset.tag: CNU7111JLR dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx7400 (GF451LA#ABM) dmi.product.version: F.0A dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Sep 29 07:53:46 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputTV-0 VGA-0 xserver.version: 2:1.14.2.901-2ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1232726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
On asus eeepc 11.10 atom cpu, I continue to have problems, the background of the dash is black, if I change my wallpaper is displayed correctly, there is no solution to this vexing probema? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Confirmed Status in Release Notes for Ubuntu: Invalid Status in “mesa” package in Ubuntu: Fix Released Status in “nux” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1105392] Re: Non-native screen resolutions unavailable when using nVidia proprietary
*** This bug is a duplicate of bug 1094905 *** https://bugs.launchpad.net/bugs/1094905 I managed to solve the same issue by manually installing the Nvidia version 319.49 drivers downloaded from http://www.nvidia.com/Download/index.aspx?lang=en-us following the procedure described in ["Method 4: Manual install from the official site"][1] Note that I have enabled the DKMS option during install, and answered yes to the question on whether to overwrite existing xorg.conf files. After installing, I rebooted the laptop and in nvidia-settings all resolutions were visible again. [1]: http://www.dedoimedo.com/computers/ubuntu-ringtail-nvidia.html So it might well worth trying to package this 319.49 version as a debian/ubuntu package... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1105392 Title: Non-native screen resolutions unavailable when using nVidia proprietary Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: Using the nVidia proprietary display driver, I am unable to change my screen resolution; only the native resolution is available: $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) LVDS-0 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1920x1200 60.0*+ DVI-I-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) The nouveau driver does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nvidia-current 304.51.really.304.43-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Fri Jan 25 14:38:53 2013 InstallationDate: Installed on 2012-12-15 (41 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: nvidia-graphics-drivers UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.current.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1105392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1173574] Re: Can't transfer music to external device
*** This bug is a duplicate of bug 1132215 *** https://bugs.launchpad.net/bugs/1132215 ** This bug has been marked a duplicate of bug 1132215 rhythmbox crashes when syncing library to ipod -- 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/1173574 Title: Can't transfer music to external device Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: I've got an SD card with an .is_audio_player file on it. Rhythmbox shows the SD card in the "devices" tab. However, dragging music files there will make Rhythmbox crash. (rhythmbox:7911): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed (rhythmbox:7911): GLib-GObject-WARNING **: g_object_set_valist: construct property "encoding-target" for object `RBTrackTransferBatch' can't be set after construction Speicherzugriffsfehler (Speicherabzug geschrieben) It fails in 12.10 (amd64) and 13.04 (amd64) while working fine on my laptop running 12.04 LTS (i386). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 27 13:55:43 2013 InstallationDate: Installed on 2012-05-23 (338 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to raring on 2013-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1173574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1131246] Re: fglrx (not installed): fglrx kernel module failed to build
I tried installing the drivers from the "software sorces"(I don't know how's it called in english, that's a literal tranlation from italian). Normal fglrx installed but nothing changed in terms of performance.When I rebooted after installing fglrx-updates and I logged ubuntu said compiz had crashed, so windows' borders, the bar on the top, and the launcher bar didn't work (using the terminal I returned to the open drivers. I was trying that version of Catalyst because the newer ones (like the 13.1) said "no supported adapters detected" and I'm using an AMD radeon HD 7450, that should be supported. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1131246 Title: fglrx (not installed): fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: trying to install catalyst 12.4 un ubuntu 12.10 I get this error ProblemType: Package DistroRelease: Ubuntu 12.10 Package: fglrx 2:8.961-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSKernelVersion: 3.5.0-21-generic Date: Thu Feb 21 16:24:35 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: fglrx, 8.961: added GraphicsCard: Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 7400 Series] [1002:677b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:249f] InstallationDate: Installed on 2012-11-26 (86 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard p6-2312el MarkForUpload: True PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=2e9203a8-b83b-4542-9464-0573af420737 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx (not installed): fglrx kernel module failed to build UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number of failed request: 25 Current serial number in output stream: 26 UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 08/29/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.07 dmi.board.name: 2ADA dmi.board.vendor: Foxconn dmi.board.version: 1.00 dmi.chassis.asset.tag: CZC2388M2J dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.07:bd08/29/2012:svnHewlett-Packard:pnp6-2312el:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6-2312el dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1131246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
