[Desktop-packages] [Bug 2009145] Re: Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored
There's this linked bug in Debian: https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17 -- 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/2009145 Title: Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored Status in xorg package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: Fix Released Bug description: Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17 The dbus-x11 package is being deprecated. As a result, the Xfce packages from upstream Debian no longer pull it in. Until the xorg packages have been updated accordingly in Ubuntu, the Xubuntu settings found in /etc/xdg/xdg-xubuntu are ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2009145/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861609] Re: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRI
I'd like to note that, on Xubuntu at least, these crashes are eliminated by removing libva-wayland2. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2013071/comments/9 -- 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/1861609 Title: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. and call stack comes from DRIMoveBuffersHelper WORKAROUND Select 'Ubuntu on Wayland' on the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1861609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
Super low priority and doesn't really fix anything. Declining for Xubuntu. ** Changed in: xubuntu-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in edubuntu-meta package in Ubuntu: Won't Fix Status in kubuntu-meta package in Ubuntu: Fix Released Status in lubuntu-meta package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-unity-meta package in Ubuntu: New Status in ubuntucinnamon-meta package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in ubuntustudio-meta package in Ubuntu: Won't Fix Status in xubuntu-meta package in Ubuntu: Won't Fix Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009145] [NEW] Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored
Public bug reported: Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17 The dbus-x11 package is being deprecated. As a result, the Xfce packages from upstream Debian no longer pull it in. Until the xorg packages have been updated accordingly in Ubuntu, the Xubuntu settings found in /etc/xdg/xdg-xubuntu are ignored. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: lunar ** Summary changed: - Xubuntu defaults are ignored + Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored ** Description changed: Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17 The dbus-x11 package is being deprecated. As a result, the Xfce packages from upstream Debian no longer pull it in. Until the xorg packages have been updated accordingly in Ubuntu, the Xubuntu settings found in - /etc/xdg are ignored. + /etc/xdg/xdg-xubuntu are ignored. ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags added: lunar -- 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/2009145 Title: Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored Status in xorg package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17 The dbus-x11 package is being deprecated. As a result, the Xfce packages from upstream Debian no longer pull it in. Until the xorg packages have been updated accordingly in Ubuntu, the Xubuntu settings found in /etc/xdg/xdg-xubuntu are ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2009145/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2013071] [NEW] Session crash after initial login
Public bug reported: Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party software for graphics and Wi-Fi hardware and additional media formats" selected during install. When logging in for the first time, the session immediately crashes and returns to the login screen. Attempting to login again without rebooting is successful. Attempting to login again after rebooting reproduces the issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 28 07:47:04 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2023-03-28 (0 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.1-2.fc37 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu ** Description changed: Xubuntu lunar beta 20230328 When logging in for the first time, the session immediately crashes and - returns to the login screen. Attempting to login again is successful. + returns to the login screen. + + Attempting to login again without rebooting is successful. + Attempting to login again after rebooting reproduces the issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 28 07:47:04 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) -Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] + Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) + Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2023-03-28 (0 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet - Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap + Bus 001 Device
[Desktop-packages] [Bug 2013071] Re: Session crash after initial login
** Description changed: Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party software for graphics and Wi-Fi hardware and additional media formats" selected during install. When logging in for the first time, the session immediately crashes and returns to the login screen. Attempting to login again without rebooting is successful. Attempting to login again after rebooting reproduces the issue. + + The issue doesn't seem to present itself if "Install third-party software for graphics and Wi-Fi hardware and additional media formats" is not selected during install. Differences in installed packages: + - chromium-codecs-ffmpeg-extra + - gimp-help-common + - gimp-help-en + - gstreamer1.0-plugins-ugly + - gstreamer1.0-vaapi + - hyphen-en-us + - liba52-0.7.4 + - libmpeg2-4 + - libopencore-amrnb0 + - libopencore-amrwb0 + - libreoffice-help-common + - libreoffice-help-en-us + - libsidplay1v5 + - libva-wayland2 + - mythes-en-us + - thunderbird-locale-en + - thunderbird-locale-en-us + - ubuntu-restricted-addons + - wbritish + + Since it seems unlikely that the language pack packages are + interfering... maybe libva-wayland2 is to blame? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 28 07:47:04 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2023-03-28 (0 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-18-generic root=UUID=0a9a1a3f-22b7-4cef-b7d4-a193beb89089 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.1-2.fc37 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.1-2.fc37:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.0:cvnQEMU:ct1:cvrpc-q35-7.0:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- 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/2013071 Title: Session crash after initial login Status in xorg package in Ubuntu: New Bug description: Xubuntu lunar beta 20230328, GNOME Boxes 43.2, "Install third-party software for graphics and Wi-Fi hardware and additional media formats" selected during install. When logging in for the first time, the session immediately crashes and returns to the login screen. Attempting to login again without rebooting is successful. Attempting to login again after rebooting reproduces the issue. The issue doesn't seem to present itself if "Install third-party software for graphics and Wi-Fi hardware and additional media formats" is not selected during install. Differences in installed packages: - chromium-codecs-ffmpeg-extra - gimp-help-common - gimp-help-en - gstreamer1.0-plugins-ugly - gstreamer1.0-vaapi - hyphen-en-us - liba52-0.7.4 - libmpeg2-4 - libopencore-amrnb0 - libopencore-amrwb0 - libreoffice-h
[Desktop-packages] [Bug 1921920] Re: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session.
** Package changed: xubuntu-meta (Ubuntu) => xfce4-session (Ubuntu) -- 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/1921920 Title: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session. Status in lightdm package in Ubuntu: New Status in xfce4-session package in Ubuntu: New Bug description: I cannot log out, shut down or restart from an activated temporary guest session. Only via tty or REISUB. Clicking anything in the logout/restart/shutdown GUI dialog window will only result in the message "An error occurred while logging out" GDBus.Error:org.freedesktop.Dbus.Error.InvalidArgs: Type ofmessage, "(yb)", does not match expected type "(b)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1921920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425972] Re: Firefox no longer supports -remote parameter
** Description changed:
+ [Impact]
+ As of Firefox version 36, the -remote commandline parameter was dropped.
This parameter is used in versions of exo prior to 0.10.3. Because of this,
opening any URLs via exo-open will cause a new firefox window to launch at the
home screen.
+
+ As reported, this affects the terminal, ubuntu-bug, xchat, and numerous
+ other applications.
+
+ [Test Case]
+ 1. Set Firefox as the default web browser in "Preferred Applications".
+ 2. From a terminal, type the following:
+
+ exo-open "http://www.xfce.org";
+
+ Expected: Firefox opens at http://www.xfce.org
+ Actual: Firefox opens at the home page.
+
+ [Regression Potential]
+ No regressions by this change. This fixes the application call to correctly
open URLs.
+
+ ---
+
+ [Original Report]
When I click a link from an email it does not work any more.
Instead of opening the link in a new tab, Firefox opens a new empty
window and does not follow the link.
If I change the default browser for my desktop from Firefox to Chrome,
then Chrome can open the link fine.
I have started seeing this today since firefox was upgraded from v35 to
36.
My email client is Mozilla thunderbird at the latest stable version.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 36.0+build2-0ubuntu0.14.10.4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: dpottage 3729 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: dpottage 3729 F pulseaudio
BuildID: 20150224133805
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Feb 26 14:30:41 2015
ForcedLayersAccel: False
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
IncompatibleExtensions:
- English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
- English (GB) Language Pack - langpack-en...@firefox.mozilla.org
- Français Language Pack - langpack...@firefox.mozilla.org
- Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
- Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
+ English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
+ English (GB) Language Pack - langpack-en...@firefox.mozilla.org
+ Français Language Pack - langpack...@firefox.mozilla.org
+ Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
+ Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-07-02 (604 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
IpRoute:
- default via 192.168.1.254 dev eth0 proto static
- 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric
1
+ default via 192.168.1.254 dev eth0 proto static
+ 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric
1
MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304
Plugins:
- Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
- LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so
(browser-plugin-libreoffice)
- Java(TM) Plug-in 11.25.2 -
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
+ Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
+ LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so
(browser-plugin-libreoffice)
+ Java(TM) Plug-in 11.25.2 -
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use)
RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1
RfKill:
- 0: phy0: Wireless LAN
- Soft blocked: yes
- Hard blocked: no
+ 0: phy0: Wireless LAN
+ Soft blocked: yes
+ Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304
UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XR1GT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 270
dmi.sys.vendor: Dell Inc.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1425972
Title:
Firefox no longer supports -remote parameter
Status in exo:
Fix Released
Status in One Hundred Papercuts:
Confirmed
Status in emacs24 package in Ubuntu:
Confirm
[Desktop-packages] [Bug 1425972] Re: Firefox no longer supports -remote parameter
** Changed in: exo (Ubuntu Utopic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1425972
Title:
Firefox no longer supports -remote parameter
Status in exo:
Fix Released
Status in One Hundred Papercuts:
Confirmed
Status in emacs24 package in Ubuntu:
Confirmed
Status in exo package in Ubuntu:
Confirmed
Status in emacs24 source package in Trusty:
Confirmed
Status in exo source package in Trusty:
Confirmed
Status in emacs24 source package in Utopic:
Confirmed
Status in exo source package in Utopic:
In Progress
Bug description:
[Impact]
As of Firefox version 36, the -remote commandline parameter was dropped.
This parameter is used in versions of exo prior to 0.10.3. Because of this,
opening any URLs via exo-open will cause a new firefox window to launch at the
home screen.
As reported, this affects the terminal, ubuntu-bug, xchat, and
numerous other applications.
[Test Case]
1. Set Firefox as the default web browser in "Preferred Applications".
2. From a terminal, type the following:
exo-open "http://www.xfce.org";
Expected: Firefox opens at http://www.xfce.org
Actual: Firefox opens at the home page.
[Regression Potential]
No regressions by this change. This fixes the application call to correctly
open URLs.
---
[Original Report]
When I click a link from an email it does not work any more.
Instead of opening the link in a new tab, Firefox opens a new empty
window and does not follow the link.
If I change the default browser for my desktop from Firefox to Chrome,
then Chrome can open the link fine.
I have started seeing this today since firefox was upgraded from v35
to 36.
My email client is Mozilla thunderbird at the latest stable version.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 36.0+build2-0ubuntu0.14.10.4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpottage 3729 F pulseaudio
BuildID: 20150224133805
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Feb 26 14:30:41 2015
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-07-02 (604 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
IpRoute:
default via 192.168.1.254 dev eth0 proto static
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric
1
MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so
(browser-plugin-libreoffice)
Java(TM) Plug-in 11.25.2 -
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use)
RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304
UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XR1GT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 270
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/exo/+bug/1425972/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425972] Re: Firefox no longer supports -remote parameter
Attaching debdiff for trusty.
** Patch added: "debdiff for trusty 14.04.2"
https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1425972/+attachment/4334749/+files/exo-trusty_14.04.2.debdiff
** Changed in: exo (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1425972
Title:
Firefox no longer supports -remote parameter
Status in exo:
Fix Released
Status in One Hundred Papercuts:
Confirmed
Status in emacs24 package in Ubuntu:
Confirmed
Status in exo package in Ubuntu:
Confirmed
Status in emacs24 source package in Trusty:
Confirmed
Status in exo source package in Trusty:
In Progress
Status in emacs24 source package in Utopic:
Confirmed
Status in exo source package in Utopic:
In Progress
Bug description:
[Impact]
As of Firefox version 36, the -remote commandline parameter was dropped.
This parameter is used in versions of exo prior to 0.10.3. Because of this,
opening any URLs via exo-open will cause a new firefox window to launch at the
home screen.
As reported, this affects the terminal, ubuntu-bug, xchat, and
numerous other applications.
[Test Case]
1. Set Firefox as the default web browser in "Preferred Applications".
2. From a terminal, type the following:
exo-open "http://www.xfce.org";
Expected: Firefox opens at http://www.xfce.org
Actual: Firefox opens at the home page.
[Regression Potential]
No regressions by this change. This fixes the application call to correctly
open URLs.
---
[Original Report]
When I click a link from an email it does not work any more.
Instead of opening the link in a new tab, Firefox opens a new empty
window and does not follow the link.
If I change the default browser for my desktop from Firefox to Chrome,
then Chrome can open the link fine.
I have started seeing this today since firefox was upgraded from v35
to 36.
My email client is Mozilla thunderbird at the latest stable version.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 36.0+build2-0ubuntu0.14.10.4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpottage 3729 F pulseaudio
BuildID: 20150224133805
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Feb 26 14:30:41 2015
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-07-02 (604 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
IpRoute:
default via 192.168.1.254 dev eth0 proto static
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric
1
MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so
(browser-plugin-libreoffice)
Java(TM) Plug-in 11.25.2 -
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use)
RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304
UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XR1GT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 270
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/exo/+bug/1425972/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled
@fkervin The bug status is still not marked as fixed. There has not been a valid fix that doesn't cause a regression. -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1173727] Re: exo-open does not handle URIs properly
This bug was fixed in exo 0.10.3, included in Vivid. ** Changed in: exo (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1173727 Title: exo-open does not handle URIs properly Status in exo: Fix Released Status in exo package in Ubuntu: Fix Released Status in xdg-utils package in Ubuntu: Invalid Bug description: when executing xdg-open "magnet:?... xdg-open detects XFCE display manager and calls exo-open "$1" witch is not capable to handle magnets at all. should it call gnome-open with xubuntu? quick fix: edit /usr/bin/xdg-open and change if [ x"$DE" = x"" ]; then DE=generic fi to if [ x"$DE" = x"" ]; then DE=generic fi DE=gnome ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xdg-utils 1.1.0~rc1-2ubuntu7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 27 22:08:40 2013 InstallationDate: Installed on 2013-04-11 (16 days ago) InstallationMedia: Xubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to raring on 2013-04-25 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1173727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398619] Re: No indicators displayed when systemd-sysv is installed
** Also affects: lightdm-gtk-greeter Importance: Undecided Status: New ** Changed in: lightdm-gtk-greeter Milestone: None => 2.0.0 ** Changed in: lightdm-gtk-greeter Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1398619 Title: No indicators displayed when systemd-sysv is installed Status in LightDM GTK+ Greeter: Fix Released Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Fix Released Status in xfce4-indicator-plugin package in Ubuntu: Fix Released Bug description: s/init/upstart/ To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1398619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
Liviu, this is an issue I had found while investigating this issue.. Can you test if the patch I posted in comment 7 https://bugzilla.xfce.org/show_bug.cgi?id=11107#c7 fixes the issue for you? -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in xfce4-settings package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114406] Re: Gtk.TreeModelSort does not init properly
Hi Martin, is it possible to make a patch available in precise? Surely this is not the only python-gtk3 application that uses a sortable treeview. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1114406 Title: Gtk.TreeModelSort does not init properly Status in Python bindings for GObject: Unknown Status in “pygobject” package in Ubuntu: Fix Released Bug description: In python-gi, attempting to use Gtk.TreeModelSort(child_model), raises TypeError, saying it takes no arguments. This is incorrect. Gtk.TreeModelSort uses a child model as its argument. This works correctly in both quantal and raring, but not precise. The init api is still the same from pyGTK... http://www.pygtk.org/docs/pygtk/class-gtktreemodelsort.html Example code: from gi.repository import Gtk model = Gtk.ListStore(GdkPixbuf.Pixbuf, str, str, str, float, str, bool, bool) sort = Gtk.TreeModelSort(model) Raises: TypeError: GObject.__init__() takes exactly 0 arguments (1 given) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.2-1~precise ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Sun Feb 3 10:48:09 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1114406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114406] Re: Gtk.TreeModelSort does not init properly
Oh, I somehow missed that. Yes, that does indeed work in precise as well. Thanks for your help Martin! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1114406 Title: Gtk.TreeModelSort does not init properly Status in Python bindings for GObject: Unknown Status in “pygobject” package in Ubuntu: Fix Released Bug description: In python-gi, attempting to use Gtk.TreeModelSort(child_model), raises TypeError, saying it takes no arguments. This is incorrect. Gtk.TreeModelSort uses a child model as its argument. This works correctly in both quantal and raring, but not precise. The init api is still the same from pyGTK... http://www.pygtk.org/docs/pygtk/class-gtktreemodelsort.html Example code: from gi.repository import Gtk model = Gtk.ListStore(GdkPixbuf.Pixbuf, str, str, str, float, str, bool, bool) sort = Gtk.TreeModelSort(model) Raises: TypeError: GObject.__init__() takes exactly 0 arguments (1 given) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.2-1~precise ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Sun Feb 3 10:48:09 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1114406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114406] [NEW] Gtk.TreeModelSort does not init properly
Public bug reported: In python-gi, attempting to use Gtk.TreeModelSort(child_model), raises TypeError, saying it takes no arguments. This is incorrect. Gtk.TreeModelSort uses a child model as its argument. This works correctly in both quantal and raring, but not precise. The init api is still the same from pyGTK... http://www.pygtk.org/docs/pygtk /class-gtktreemodelsort.html Example code: from gi.repository import Gtk model = Gtk.ListStore(GdkPixbuf.Pixbuf, str, str, str, float, str, bool, bool) sort = Gtk.TreeModelSort(model) Raises: TypeError: GObject.__init__() takes exactly 0 arguments (1 given) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.2-1~precise ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Sun Feb 3 10:48:09 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1114406 Title: Gtk.TreeModelSort does not init properly Status in “pygobject” package in Ubuntu: New Bug description: In python-gi, attempting to use Gtk.TreeModelSort(child_model), raises TypeError, saying it takes no arguments. This is incorrect. Gtk.TreeModelSort uses a child model as its argument. This works correctly in both quantal and raring, but not precise. The init api is still the same from pyGTK... http://www.pygtk.org/docs/pygtk/class-gtktreemodelsort.html Example code: from gi.repository import Gtk model = Gtk.ListStore(GdkPixbuf.Pixbuf, str, str, str, float, str, bool, bool) sort = Gtk.TreeModelSort(model) Raises: TypeError: GObject.__init__() takes exactly 0 arguments (1 given) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.2-1~precise ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 Date: Sun Feb 3 10:48:09 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1114406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1002706] Re: Language setting ignored
** Also affects: lightdm-gtk-greeter 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/1002706 Title: Language setting ignored Status in LightDM GTK+ Greeter: New Status in “lightdm” package in Ubuntu: New Status in “lightdm-gtk-greeter” package in Ubuntu: New Bug description: The language setting chosen at login is ignored for user accounts whose home directory has been encrypted, and will always be the system's default (in my case, English - Great Britain). Users whose home directory hasn't been encrypted can change the language successfully at login. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm-gtk-greeter 1.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 22 08:29:23 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1002706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1002706] Re: Language setting ignored
** Changed in: lightdm-gtk-greeter Status: New => Confirmed ** Changed in: lightdm-gtk-greeter Importance: Undecided => Medium -- 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/1002706 Title: Language setting ignored Status in LightDM GTK+ Greeter: Confirmed Status in “lightdm” package in Ubuntu: New Status in “lightdm-gtk-greeter” package in Ubuntu: New Bug description: The language setting chosen at login is ignored for user accounts whose home directory has been encrypted, and will always be the system's default (in my case, English - Great Britain). Users whose home directory hasn't been encrypted can change the language successfully at login. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm-gtk-greeter 1.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 22 08:29:23 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1002706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1024482] Re: Mouse cursor theme does not change from default after login
** Changed in: lightdm-gtk-greeter Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1024482 Title: Mouse cursor theme does not change from default after login Status in LightDM GTK+ Greeter: Confirmed Status in “unity-greeter” package in Ubuntu: Confirmed Status in “lightdm” package in Debian: Confirmed Status in “lightdm-gtk-greeter” package in Debian: Confirmed Bug description: When using LightDM to login to a GNOME Shell session, the mouse cursor's appearance does not change from what it is in the lightdm login screen (black pointer from default X theme). Any custom mouse cursor theme actually does apply within any open application windows, but hovering the cursor over the window title bar, the root window, or the Shell interface changes it back to the default black pointer, leading to an inconsistent appearance. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1024482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296276] Re: light-locker fails to properly renew kerberos tickets with pam-krb5
This may actually be a bug in lightdm. Including it in the bug report. ** Also 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/1296276 Title: light-locker fails to properly renew kerberos tickets with pam-krb5 Status in “light-locker” package in Ubuntu: New Status in “lightdm” package in Ubuntu: New Bug description: I am using the pam-krb5 module to log into a Kerberos realm using lightdm. This works the initial time I log in, when I come in through lightdm. However, once I am logged in, and I lock the screen using light-locker, when I unlock the screen I no longer get renewed tickets. The problem seems to be this: -rw--- 1 me me 504 Mar 23 08:37 krb5cc_1000_sjkfhagfg -rw--- 1 root root504 Mar 23 08:38 krb5cc_pam_lsdkjhfsdk So what is happening is that on the initial login, I get a valid ticket cache, owned by my logging-in user, and showing my UID in the file name. This ticket works fine. However, once I lock the screen and then unlock it, I get a ticket cache owned by root, with "_pam_" in the filename, and of course I can't use it because I am not logged in as root. This problem did not occur in 12.04 LTS, probably because it did not use light-locker. The pam-krb5 module works in all other cases in my installations, so I do not believe this is any kind of problem with the pam_krb5 module. Thanks, Brian ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-locker 1.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Sun Mar 23 08:40:38 2014 InstallationDate: Installed on 2014-03-22 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140320) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1296276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1267742] Re: Screen artifacts appear after restart and cold boot
** Changed in: lightdm-gtk-greeter Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1267742 Title: Screen artifacts appear after restart and cold boot Status in LightDM GTK+ Greeter: Fix Released Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: When I cold boot the login screen background is garbled - see screenshot attached ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 10 08:21:28 2014 InstallationDate: Installed on 2013-12-25 (15 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131225) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1267742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1264563] Re: switch-to-greeter does not set lock hint
** Changed in: lightdm-gtk-greeter Status: Fix Committed => Fix Released -- 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/1264563 Title: switch-to-greeter does not set lock hint Status in LightDM GTK+ Greeter: Fix Released Status in “lightdm” package in Ubuntu: Invalid Bug description: light-locker is able to lock the current user session automatically on suspend/hibernation and it works as expected. However, after resuming the system lightdm-gtk-greeter displays the "Log In" button instead of the "Unlock" one and does not highlight the current logged in user. This does not seem to affect the login/unlock process and was only tested with hibernation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-locker 1.0.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: XFCE Date: Fri Dec 27 19:15:50 2013 InstallationDate: Installed on 2013-09-21 (97 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130920) SourcePackage: light-locker UpgradeStatus: Upgraded to trusty on 2013-11-08 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1264563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1264563] Re: switch-to-greeter does not set lock hint
** Changed in: lightdm-gtk-greeter Milestone: None => 1.7.1 -- 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/1264563 Title: switch-to-greeter does not set lock hint Status in LightDM GTK+ Greeter: Fix Committed Status in “lightdm” package in Ubuntu: Invalid Bug description: light-locker is able to lock the current user session automatically on suspend/hibernation and it works as expected. However, after resuming the system lightdm-gtk-greeter displays the "Log In" button instead of the "Unlock" one and does not highlight the current logged in user. This does not seem to affect the login/unlock process and was only tested with hibernation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-locker 1.0.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: XFCE Date: Fri Dec 27 19:15:50 2013 InstallationDate: Installed on 2013-09-21 (97 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130920) SourcePackage: light-locker UpgradeStatus: Upgraded to trusty on 2013-11-08 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1264563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226544] [NEW] lightdm --test-mode fails immediately
Public bug reported: When attempting to run lightdm --test-mode, a window is shown for a split second and then closes. I have xserver-xephyr installed, this happens with either lightdm-gtk-greeter and unity-greeter. lightdm 1.7.15-0ubuntu1 lightdm-gtk-greeter 1.6.1+133+97~ubuntu13.10.1 (from daily build) unity-greeter 13.10.2-0ubuntu1 xserver-xephyr 2:1.14.2.901-2ubuntu4 I have attached lightdm.log from ~/.cache/lightdm/log ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Tue Sep 17 07:00:33 2013 InstallationDate: Installed on 2013-09-14 (2 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130914) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=xubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1226544 Title: lightdm --test-mode fails immediately Status in “lightdm” package in Ubuntu: New Bug description: When attempting to run lightdm --test-mode, a window is shown for a split second and then closes. I have xserver-xephyr installed, this happens with either lightdm-gtk-greeter and unity-greeter. lightdm 1.7.15-0ubuntu1 lightdm-gtk-greeter 1.6.1+133+97~ubuntu13.10.1 (from daily build) unity-greeter 13.10.2-0ubuntu1 xserver-xephyr 2:1.14.2.901-2ubuntu4 I have attached lightdm.log from ~/.cache/lightdm/log ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Tue Sep 17 07:00:33 2013 InstallationDate: Installed on 2013-09-14 (2 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130914) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=xubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1226544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226544] Re: lightdm --test-mode fails immediately
lightdm-gtk-greeter log ** Attachment added: "lightdm-gtk-greeter lightdm.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1226544/+attachment/3825171/+files/lightdm-gtk-greeter-lightdm.log -- 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/1226544 Title: lightdm --test-mode fails immediately Status in “lightdm” package in Ubuntu: New Bug description: When attempting to run lightdm --test-mode, a window is shown for a split second and then closes. I have xserver-xephyr installed, this happens with either lightdm-gtk-greeter and unity-greeter. lightdm 1.7.15-0ubuntu1 lightdm-gtk-greeter 1.6.1+133+97~ubuntu13.10.1 (from daily build) unity-greeter 13.10.2-0ubuntu1 xserver-xephyr 2:1.14.2.901-2ubuntu4 I have attached lightdm.log from ~/.cache/lightdm/log ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Tue Sep 17 07:00:33 2013 InstallationDate: Installed on 2013-09-14 (2 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130914) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=xubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1226544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226544] Re: lightdm --test-mode fails immediately
unity-greeter log ** Attachment added: "unity-greeter lightdm.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1226544/+attachment/3825170/+files/unity-greeter-lightdm.log -- 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/1226544 Title: lightdm --test-mode fails immediately Status in “lightdm” package in Ubuntu: New Bug description: When attempting to run lightdm --test-mode, a window is shown for a split second and then closes. I have xserver-xephyr installed, this happens with either lightdm-gtk-greeter and unity-greeter. lightdm 1.7.15-0ubuntu1 lightdm-gtk-greeter 1.6.1+133+97~ubuntu13.10.1 (from daily build) unity-greeter 13.10.2-0ubuntu1 xserver-xephyr 2:1.14.2.901-2ubuntu4 I have attached lightdm.log from ~/.cache/lightdm/log ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Tue Sep 17 07:00:33 2013 InstallationDate: Installed on 2013-09-14 (2 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130914) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=xubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1226544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1152927] [NEW] NetworkManager does not detect ethernet connected
Public bug reported: NetworkManager detects when an ethernet connection is lost, but is anable to restore a connection when the cable is reconnected. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Sat Mar 9 06:31:24 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-03-09 (0 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308) IpRoute: default via 192.168.1.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.111 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH BlueSabreNet 67f55344-0f2f-4d59-895b-612c8b74340f 802-11-wireless 1362828481 Sat 09 Mar 2013 06:28:01 AM ESTyes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 15360ee5e-3fe0-4e82-9fd5-3c9515c22ea6 802-3-ethernet1362828374 Sat 09 Mar 2013 06:26:14 AM ESTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1152927 Title: NetworkManager does not detect ethernet connected Status in “network-manager” package in Ubuntu: New Bug description: NetworkManager detects when an ethernet connection is lost, but is anable to restore a connection when the cable is reconnected. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Sat Mar 9 06:31:24 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-03-09 (0 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308) IpRoute: default via 192.168.1.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.111 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH BlueSabreNet 67f55344-0f2f-4d59-895b-612c8b74340f 802-11-wireless 1362828481 Sat 09 Mar 2013 06:28:01 AM ESTyes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 15360ee5e-3fe0-4e82-9fd5-3c9515c22ea6 802-3-ethernet1362828374 Sat 09 Mar 2013 06:26:14 AM ESTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sou
[Desktop-packages] [Bug 818852] Re: X cursor often not shown
Please test this again. With the latest changes to the greeter, GTK, and X this problem should be resolved. -- 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/818852 Title: X cursor often not shown Status in LightDM GTK+ Greeter: Triaged Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” package in Arch Linux: New Status in “lightdm” package in Debian: Fix Released Bug description: It seems that, since 0.9.2, cursor is often not shown in GTK+ greeter. This is a regression from 0.9.0, afaict, but it might be a GTK+ 3.0 issue too. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/818852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1320560] Re: Removal of gdmflexiserver breaks user switching
Patches have been updated on the PPA. Please test before I upload to the archive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1320560 Title: Removal of gdmflexiserver breaks user switching Status in “xfce4-panel” package in Ubuntu: Confirmed Status in “xfce4-whiskermenu-plugin” package in Ubuntu: Confirmed Status in “xfswitch-plugin” package in Ubuntu: Confirmed Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Hello and pardon for my bad english. On xfce4, the button to log with a new user without logout never wants to works. It accepts to open a confirmation windows "To you really want to change user?" That's OK. Then I press Yes and I've got an error message who says in french : "Impossible to create a new display" and in english : "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files" lsb_release-rd : Description:Ubuntu 14.04 LTS Release:14.04 apt-cache policy xfswitch-plugin xfswitch-plugin: Installé : 0.0.1-4ubuntu1 Candidat : 0.0.1-4ubuntu1 Table de version : *** 0.0.1-4ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status Thanks for your help. Claude Micouin ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfswitch-plugin 0.0.1-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 18 00:20:57 2014 InstallationDate: Installed on 2014-05-07 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfswitch-plugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1320560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1320560] Re: Removal of gdmflexiserver breaks user switching
Attaching debdiff for xfswitch-plugin on Utopic, request package sponsorship. ** Patch added: "xfswitch-plugin utopic debdiff" https://bugs.launchpad.net/ubuntu/+source/xfswitch-plugin/+bug/1320560/+attachment/4235588/+files/xfswitch-plugin_0.0.1-5ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1320560 Title: Removal of gdmflexiserver breaks user switching Status in “xfce4-panel” package in Ubuntu: Confirmed Status in “xfce4-whiskermenu-plugin” package in Ubuntu: Confirmed Status in “xfswitch-plugin” package in Ubuntu: Confirmed Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Hello and pardon for my bad english. On xfce4, the button to log with a new user without logout never wants to works. It accepts to open a confirmation windows "To you really want to change user?" That's OK. Then I press Yes and I've got an error message who says in french : "Impossible to create a new display" and in english : "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files" lsb_release-rd : Description:Ubuntu 14.04 LTS Release:14.04 apt-cache policy xfswitch-plugin xfswitch-plugin: Installé : 0.0.1-4ubuntu1 Candidat : 0.0.1-4ubuntu1 Table de version : *** 0.0.1-4ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status Thanks for your help. Claude Micouin ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfswitch-plugin 0.0.1-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 18 00:20:57 2014 InstallationDate: Installed on 2014-05-07 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfswitch-plugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1320560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1320560] Re: Removal of gdmflexiserver breaks user switching
@laney -- Yes, will forward packages upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1320560 Title: Removal of gdmflexiserver breaks user switching Status in “xfce4-panel” package in Ubuntu: Confirmed Status in “xfce4-whiskermenu-plugin” package in Ubuntu: Confirmed Status in “xfswitch-plugin” package in Ubuntu: Confirmed Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Hello and pardon for my bad english. On xfce4, the button to log with a new user without logout never wants to works. It accepts to open a confirmation windows "To you really want to change user?" That's OK. Then I press Yes and I've got an error message who says in french : "Impossible to create a new display" and in english : "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files" lsb_release-rd : Description:Ubuntu 14.04 LTS Release:14.04 apt-cache policy xfswitch-plugin xfswitch-plugin: Installé : 0.0.1-4ubuntu1 Candidat : 0.0.1-4ubuntu1 Table de version : *** 0.0.1-4ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status Thanks for your help. Claude Micouin ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfswitch-plugin 0.0.1-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 18 00:20:57 2014 InstallationDate: Installed on 2014-05-07 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfswitch-plugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1320560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1320560] Re: Removal of gdmflexiserver breaks user switching
Attaching debdiff for xscreensaver on Utopic. Request package sponsorship. ** Patch added: "debdiff for xscreensaver on Utopic" https://bugs.launchpad.net/ubuntu/+source/xfswitch-plugin/+bug/1320560/+attachment/4235589/+files/xscreensaver_5.26-1ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1320560 Title: Removal of gdmflexiserver breaks user switching Status in “xfce4-panel” package in Ubuntu: Confirmed Status in “xfce4-whiskermenu-plugin” package in Ubuntu: Confirmed Status in “xfswitch-plugin” package in Ubuntu: Confirmed Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Hello and pardon for my bad english. On xfce4, the button to log with a new user without logout never wants to works. It accepts to open a confirmation windows "To you really want to change user?" That's OK. Then I press Yes and I've got an error message who says in french : "Impossible to create a new display" and in english : "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files" lsb_release-rd : Description:Ubuntu 14.04 LTS Release:14.04 apt-cache policy xfswitch-plugin xfswitch-plugin: Installé : 0.0.1-4ubuntu1 Candidat : 0.0.1-4ubuntu1 Table de version : *** 0.0.1-4ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status Thanks for your help. Claude Micouin ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfswitch-plugin 0.0.1-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 18 00:20:57 2014 InstallationDate: Installed on 2014-05-07 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfswitch-plugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1320560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
I've tested the patch, and noticed that without the patch xfsettingsd sometimes crashes when an external display (in this case, a TV) is unplugged. Without the patch, xfsettingsd no longer crashes. -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “xfce4-settings” package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330037] Re: [FFe] upower 0.99.1 transition
As Xubuntu Technical Lead and on behalf of the Xubuntu Release Team, I too would like to strongly object to this FFe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: [FFe] upower 0.99.1 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “cinnamon-control-center” package in Ubuntu: New Status in “cinnamon-session” package in Ubuntu: New Status in “cinnamon-settings-daemon” package in Ubuntu: New Status in “gnome-applets” package in Ubuntu: In Progress Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “gnome-shell-pomodoro” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Released Status in “mate-power-manager” package in Ubuntu: Fix Released Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: In Progress Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “xfce4-weather-plugin” package in Ubuntu: Invalid Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops the suspend/hibernate functions, as logind now does that. All major DEs have support for this,so nearly everything just needs a rebuild. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed All packages (and build logs) are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. gnome-power-manager: Fixed in newest upstream release. Merge from debian gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart, no rebuilds needed cinnamon: Rebuild mate: all mate packages need rebuilding python-dbusmock: needs rebuild sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, so it's done wmbattery: needs rebuild xfce4-power-manager: Needs rebuilding xfce4-session: Fixed already, since we switched to logind xfce4-settings: Needs rebuild xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308105]
Created attachment 5723 HDMI and Screen On Event Patch I think I figured out the failure in the logic. You are right, since we are clearing the caches in that particular function, it makes sense to make sure they are truly freed. The above fix uncovered another issue with the order of events when the "Configure new displays when connected" feature is enabled. I found that we are clearing our caches in the middle of the screen event (thats the leftover reference you found). I reordered the code for that function, and now I think I should have a fully functional patch. Please try the attached patch and let me know if the issue is still resolved for you. -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Confirmed Status in xfce4-settings: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-331” package in Ubuntu: Invalid Status in “xfce4-settings” package in Ubuntu: Confirmed Bug description: I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new behavior that if the TV is power cycled it no longer detects a link with the HTPC. When this happens I can find in the xorg log that there is an accompanying log item: [ 39829.509] (II) NVIDIA(0): Setting mode "NULL" After debugging with NVIDIA at https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being- detected/ we've deteremined it's a X client that reacts to the RANDR events causing the mode to be set to NULL. Working through the list in an Xfce environment, the culprit is xfsettingsd. If xfsettingsd is running, it causes the TV to come up in a NULL mode. If it's killed, it remains in the mode it was previously running in. Until this is fixed, this behavior can be worked around with a simple shell script: == #!/bin/sh #Fix TV state when HDMI link is lost. #By Mario Limonciello OUTPUT="HDMI-0" BAD_MODE="1280x720" GOOD_MODE="1920x1080" for MODE in $BAD_MODE $GOOD_MODE; do DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE sleep 2 done == To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
The first of the two merge proposals has been released in lightdm-gtk- greeter 1.8.2 ** Also affects: lightdm-gtk-greeter Importance: Undecided Status: New ** Changed in: lightdm-gtk-greeter Status: New => Fix Released ** Changed in: lightdm-gtk-greeter Importance: Undecided => Low ** Changed in: lightdm-gtk-greeter Assignee: (unassigned) => Sean Davis (smd-seandavis) ** Changed in: lightdm-gtk-greeter Milestone: None => 1.8.2 ** Changed in: lightdm-gtk-greeter Status: Fix Released => In Progress -- 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/1276072 Title: Language selection always falls back to English Status in LightDM GTK+ Greeter: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm-gtk-greeter” package in Ubuntu: In Progress Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK & US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
** Changed in: lightdm-gtk-greeter Status: In Progress => Fix Released -- 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/1276072 Title: Language selection always falls back to English Status in LightDM GTK+ Greeter: Fix Released Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm-gtk-greeter” package in Ubuntu: In Progress Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK & US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 948612] [NEW] gnome-terminal does not scroll with mousewheel
Public bug reported: When attempting to scroll in gnome-terminal with the mousewheel, nothing happens. Clicking the "scroll up" button on the overlay scrollbar does work as expected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94-0ubuntu2 Architecture: amd64 Date: Tue Mar 6 20:10:16 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi precise -- 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/948612 Title: gnome-terminal does not scroll with mousewheel Status in “gnome-terminal” package in Ubuntu: New Bug description: When attempting to scroll in gnome-terminal with the mousewheel, nothing happens. Clicking the "scroll up" button on the overlay scrollbar does work as expected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94-0ubuntu2 Architecture: amd64 Date: Tue Mar 6 20:10:16 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/948612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 948612] Re: gnome-terminal does not scroll with mousewheel
-- 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/948612 Title: gnome-terminal does not scroll with mousewheel Status in “gnome-terminal” package in Ubuntu: New Bug description: When attempting to scroll in gnome-terminal with the mousewheel, nothing happens. Clicking the "scroll up" button on the overlay scrollbar does work as expected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94-0ubuntu2 Architecture: amd64 Date: Tue Mar 6 20:10:16 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/948612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950134] [NEW] No Help Page
Public bug reported: There is no hekp page for gcalctool, despite there being a "Contents" option in the Help Menu. Going to gcalctool Help > Contents shows "Page Not Found The page ‘index’ was not found in the document ‘help:gcalctool’." ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gcalctool 6.3.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 12:57:04 2012 ExecutablePath: /usr/bin/gcalctool InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gcalctool UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcalctool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/950134 Title: No Help Page Status in “gcalctool” package in Ubuntu: New Bug description: There is no hekp page for gcalctool, despite there being a "Contents" option in the Help Menu. Going to gcalctool Help > Contents shows "Page Not Found The page ‘index’ was not found in the document ‘help:gcalctool’." ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gcalctool 6.3.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 12:57:04 2012 ExecutablePath: /usr/bin/gcalctool InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gcalctool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/950134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950134] Re: No Help Page
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/950134 Title: No Help Page Status in “gcalctool” package in Ubuntu: New Bug description: There is no hekp page for gcalctool, despite there being a "Contents" option in the Help Menu. Going to gcalctool Help > Contents shows "Page Not Found The page ‘index’ was not found in the document ‘help:gcalctool’." ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gcalctool 6.3.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 12:57:04 2012 ExecutablePath: /usr/bin/gcalctool InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gcalctool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/950134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950149] [NEW] baobab - toolbar icon causes change in toolbar height
Public bug reported: This is for the application "baobab" - "Disk Usage Analyzer" Just a fair note: This is not always reproduceable. On occasion, when hovering over the "Scan a Folder" icon in the toolbar, the toolbar grows a few pixels. When leaving the icon, the toolbar returns to its previous size. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: baobab 3.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 13:17:51 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/950149 Title: baobab - toolbar icon causes change in toolbar height Status in “gnome-utils” package in Ubuntu: New Bug description: This is for the application "baobab" - "Disk Usage Analyzer" Just a fair note: This is not always reproduceable. On occasion, when hovering over the "Scan a Folder" icon in the toolbar, the toolbar grows a few pixels. When leaving the icon, the toolbar returns to its previous size. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: baobab 3.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 13:17:51 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/950149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950149] Re: baobab - toolbar icon causes change in toolbar height
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/950149 Title: baobab - toolbar icon causes change in toolbar height Status in “gnome-utils” package in Ubuntu: New Bug description: This is for the application "baobab" - "Disk Usage Analyzer" Just a fair note: This is not always reproduceable. On occasion, when hovering over the "Scan a Folder" icon in the toolbar, the toolbar grows a few pixels. When leaving the icon, the toolbar returns to its previous size. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: baobab 3.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 13:17:51 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/950149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 669572] Re: Gtk apps are crashing due to missing icons
Marking as invalid for catfish. gtk_image_set_from_stock should handle setting the icon, or load a missing-image icon. Please try again with the latest build and reopen the report if you still have this problem. ** Changed in: catfish (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/669572 Title: Gtk apps are crashing due to missing icons Status in Inkscape: A Vector Drawing Tool: Invalid Status in “catfish” package in Ubuntu: Invalid Status in “gedit” package in Ubuntu: Invalid Status in “inkscape” package in Ubuntu: Invalid Bug description: Since upgrading to 10.10 from 10.04, various Gtk apps (gedit, inkscape) are crashing in KDE, and the error messages are always something like this: - Could not load theme icon gtk-home: Icon 'gtk-home' not present in theme - glib.GError: Icon 'gtk-justify-left' not present in theme - Icon 'gtk-properties' not present in theme If I change my icon theme from Oxygen to gnome, they work fine of course. But somehow Oxygen is no longer falling back on gtk icons elsewhere when they don't exist in that theme. Is this a configuration issue? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: kubuntu-desktop 1.205 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Mon Nov 1 14:24:10 2010 InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/669572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969181] Re: gwibber does not scroll
Marking as invalid since its not reproducible. ** Changed in: gwibber (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/969181 Title: gwibber does not scroll Status in “gwibber” package in Ubuntu: Invalid Bug description: Gwibber does not scroll down when using mousewheel or scrollbar. Xubuntu 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Mar 30 09:06:01 2012 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/969181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 961042] [NEW] laptop no longer suspends when lid closed
Public bug reported: My Dell Latitude E6400 no longer suspends when the lid is closed. The current power settings for when the lid is closed is to suspend. However, when closing the lid, the screen just goes blank and it does not suspend. This has worked in previous versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Wed Mar 21 06:30:38 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/961042 Title: laptop no longer suspends when lid closed Status in “gnome-power-manager” package in Ubuntu: New Bug description: My Dell Latitude E6400 no longer suspends when the lid is closed. The current power settings for when the lid is closed is to suspend. However, when closing the lid, the screen just goes blank and it does not suspend. This has worked in previous versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Wed Mar 21 06:30:38 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/961042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 961042] Re: laptop no longer suspends when lid closed
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/961042 Title: laptop no longer suspends when lid closed Status in “gnome-power-manager” package in Ubuntu: New Bug description: My Dell Latitude E6400 no longer suspends when the lid is closed. The current power settings for when the lid is closed is to suspend. However, when closing the lid, the screen just goes blank and it does not suspend. This has worked in previous versions of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Wed Mar 21 06:30:38 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/961042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967023] [NEW] nautilus global menu and local menu active
Public bug reported: As of an update installed 2 days ago, nautilus now uses the global and local menu. This is (I hope) unexpected behavior? See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 07:10:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/967023 Title: nautilus global menu and local menu active Status in “nautilus” package in Ubuntu: New Bug description: As of an update installed 2 days ago, nautilus now uses the global and local menu. This is (I hope) unexpected behavior? See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 07:10:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash 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/967023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967023] Re: nautilus global menu and local menu active
** Attachment added: "Screenshot of funky behavior" https://bugs.launchpad.net/bugs/967023/+attachment/2954177/+files/Screenshot%20from%202012-03-28%2007%3A12%3A44.png -- 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/967023 Title: nautilus global menu and local menu active Status in “nautilus” package in Ubuntu: New Bug description: As of an update installed 2 days ago, nautilus now uses the global and local menu. This is (I hope) unexpected behavior? See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 07:10:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash 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/967023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967023] Re: nautilus global menu and local menu active
Yes, the bug is specific to nautilus. I don't know what all was updated that day, but some unity packages were definitely part of it (then I encountered some crazy unity bugs). Here's the .xsession-errors. ** Attachment added: "xsession errors" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/967023/+attachment/2957447/+files/.xsession-errors -- 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/967023 Title: nautilus global menu and local menu active Status in “nautilus” package in Ubuntu: Incomplete Bug description: As of an update installed 2 days ago, nautilus now uses the global and local menu. This is (I hope) unexpected behavior? See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 07:10:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash 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/967023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 967023] Re: nautilus global menu and local menu active
Strangely enough, that does seem to fix it. -- 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/967023 Title: nautilus global menu and local menu active Status in “nautilus” package in Ubuntu: Incomplete Bug description: As of an update installed 2 days ago, nautilus now uses the global and local menu. This is (I hope) unexpected behavior? See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.92-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 07:10:04 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash 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/967023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969181] [NEW] gwibber does not scroll
Public bug reported: Gwibber does not scroll down when using mousewheel or scrollbar. Xubuntu 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Mar 30 09:06:01 2012 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwibber (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/969181 Title: gwibber does not scroll Status in “gwibber” package in Ubuntu: New Bug description: Gwibber does not scroll down when using mousewheel or scrollbar. Xubuntu 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Mar 30 09:06:01 2012 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/969181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969181] Re: gwibber does not scroll
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/969181 Title: gwibber does not scroll Status in “gwibber” package in Ubuntu: New Bug description: Gwibber does not scroll down when using mousewheel or scrollbar. Xubuntu 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Mar 30 09:06:01 2012 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/969181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969181] Re: gwibber does not scroll
After switching to a different "tab" scrolling works. Weird. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/969181 Title: gwibber does not scroll Status in “gwibber” package in Ubuntu: New Bug description: Gwibber does not scroll down when using mousewheel or scrollbar. Xubuntu 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Mar 30 09:06:01 2012 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/969181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 969181] Re: gwibber does not scroll
As far as I can tell, it only happened on first load. Not having any more issues now, even after rebooting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/969181 Title: gwibber does not scroll Status in “gwibber” package in Ubuntu: Incomplete Bug description: Gwibber does not scroll down when using mousewheel or scrollbar. Xubuntu 11.10 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Mar 30 09:06:01 2012 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/969181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 974507] [NEW] Help not installed
Public bug reported: Clicking on Help in alacarte presents the following: Document Not Found The URI ‘ghelp:user-guide?menu-editor#menu-editor’ does not point to a valid page. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alacarte 0.13.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Thu Apr 5 14:18:24 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alacarte (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/974507 Title: Help not installed Status in “alacarte” package in Ubuntu: New Bug description: Clicking on Help in alacarte presents the following: Document Not Found The URI ‘ghelp:user-guide?menu-editor#menu-editor’ does not point to a valid page. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alacarte 0.13.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Thu Apr 5 14:18:24 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/974507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 974507] Re: Help not installed
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/974507 Title: Help not installed Status in “alacarte” package in Ubuntu: New Bug description: Clicking on Help in alacarte presents the following: Document Not Found The URI ‘ghelp:user-guide?menu-editor#menu-editor’ does not point to a valid page. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alacarte 0.13.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Thu Apr 5 14:18:24 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/974507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 974520] [NEW] gnomine and quadrapassel help not installed
Public bug reported: Help is not installed for gnomine and quadrapassel Click on Menu > Help and you get: Document Not Found The URI ‘help:gnomine/index’ does not point to a valid page. Document Not Found The URI ‘help:quadrapassel/index’ does not point to a valid page. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnomine 1:3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Thu Apr 5 14:37:30 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-games UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/974520 Title: gnomine and quadrapassel help not installed Status in “gnome-games” package in Ubuntu: New Bug description: Help is not installed for gnomine and quadrapassel Click on Menu > Help and you get: Document Not Found The URI ‘help:gnomine/index’ does not point to a valid page. Document Not Found The URI ‘help:quadrapassel/index’ does not point to a valid page. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnomine 1:3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Thu Apr 5 14:37:30 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-games UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/974520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 974520] Re: gnomine and quadrapassel help not installed
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/974520 Title: gnomine and quadrapassel help not installed Status in “gnome-games” package in Ubuntu: New Bug description: Help is not installed for gnomine and quadrapassel Click on Menu > Help and you get: Document Not Found The URI ‘help:gnomine/index’ does not point to a valid page. Document Not Found The URI ‘help:quadrapassel/index’ does not point to a valid page. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnomine 1:3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Thu Apr 5 14:37:30 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-games UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/974520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976942] [NEW] AppIndicator3 does not honor hidden menus
Public bug reported: gi.repository.AppIndicator3 shows "hidden" menus. If you set a menu to "hidden" or do not do menu.show(), the AppIndicator displays the menu anyway. Please let me know what additional information I can provide. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.0-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 22:14:50 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/976942 Title: AppIndicator3 does not honor hidden menus Status in “pygobject” package in Ubuntu: New Bug description: gi.repository.AppIndicator3 shows "hidden" menus. If you set a menu to "hidden" or do not do menu.show(), the AppIndicator displays the menu anyway. Please let me know what additional information I can provide. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.0-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 22:14:50 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/976942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976942] Re: AppIndicator3 does not honor hidden menus
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/976942 Title: AppIndicator3 does not honor hidden menus Status in “pygobject” package in Ubuntu: New Bug description: gi.repository.AppIndicator3 shows "hidden" menus. If you set a menu to "hidden" or do not do menu.show(), the AppIndicator displays the menu anyway. Please let me know what additional information I can provide. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-gi 3.2.0-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 22:14:50 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pygobject UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/976942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898541] Re: [FFe] Update to 3.38.0
No objections on the Xubuntu side. -- 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/1898541 Title: [FFe] Update to 3.38.0 Status in gnome-software package in Ubuntu: Fix Committed Bug description: It would be good if we could ship gnome-software 3.38.0 with groovy. These are the 3.37.92 changes: Add sysprof support for profiling jobs Add webflow and basic auth support to flatpak plugin Coalesce refresh operations where possible Correctly mark layered rpm-ostree local packages as removable Fix flatpak bundle installation Handle invalid snap auth data Improve flatpak progress reporting for transactions Improve the heuristic for detecting old-style AppStream override files Many performance improvements in many areas of the code Only delete the firmware archive if we downloaded it to the cache Show a pulsing progress bar if progress is unknown Support loading appstream files from custom install prefix Use the runtime fwupd version for the user agent 3.38.0 is a pure translation update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1898541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838008] Re: [snap] cursor theme isn't respected
** Also affects: xubuntu-default-settings (Ubuntu) Importance: Undecided Status: New -- 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/1838008 Title: [snap] cursor theme isn't respected Status in chromium-browser package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: (initially reported at https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/85) When changing the cursor theme with gnome-tweaks, I can observe that some themes aren't respected in the chromium snap. This appears to be specific to chromium, other snaps like evince or gimp use the correct cursors. Yaru and Adwaita are fine, but Redglass or Whiteglass aren't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838008] Re: [snap] cursor theme isn't respected
Fix committed in xubuntu-default-settings: - https://github.com/Xubuntu/xubuntu-default-settings/commit/7ea4e59df2394140b28cf92b2651d327a800f00f - https://github.com/Xubuntu/xubuntu-default-settings/commit/f2ee8c4526862248edba19dc8a1aca9dfa10059b Basically, we were referencing a theme that no longer exists, "Human", so the theme was falling back on Default. There is no default theme in gtk-common-themes, so the fallback X11 theme was used instead. ** Changed in: xubuntu-default-settings (Ubuntu) Status: Confirmed => Fix Committed -- 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/1838008 Title: [snap] cursor theme isn't respected Status in chromium-browser package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Fix Committed Bug description: (initially reported at https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/85) When changing the cursor theme with gnome-tweaks, I can observe that some themes aren't respected in the chromium snap. This appears to be specific to chromium, other snaps like evince or gimp use the correct cursors. Yaru and Adwaita are fine, but Redglass or Whiteglass aren't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
** Changed in: xubuntu-docs (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - apt install xubuntu-desktop does not resolve dependencies properly + Document installation of xubuntu-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: Document installation of xubuntu-desktop Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: Fix Released Status in xubuntu-docs package in Ubuntu: Triaged Status in xubuntu-meta package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838008] Re: [snap] cursor theme isn't respected
** Changed in: xubuntu-default-settings (Ubuntu) Importance: Undecided => Medium -- 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/1838008 Title: [snap] cursor theme isn't respected Status in chromium-browser package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Fix Committed Bug description: (initially reported at https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/85) When changing the cursor theme with gnome-tweaks, I can observe that some themes aren't respected in the chromium snap. This appears to be specific to chromium, other snaps like evince or gimp use the correct cursors. Yaru and Adwaita are fine, but Redglass or Whiteglass aren't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
** No longer affects: lightdm-gtk-greeter-settings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Released Status in Boot-Repair: Fix Released Status in GNOME Terminal: New Status in HPLIP: New Status in OS-Uninstaller: Fix Released Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launch
[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
** Bug watch added: LightDM GTK+ Greeter Settings Bugs #5 https://github.com/Xubuntu/lightdm-gtk-greeter-settings/issues/5 ** Also affects: lightdm-gtk-greeter-settings via https://github.com/Xubuntu/lightdm-gtk-greeter-settings/issues/5 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Released Status in Boot-Repair: Fix Released Status in GNOME Terminal: New Status in HPLIP: New Status in Settings editor for LightDM GTK+ Greeter: Unknown Status in OS-Uninstaller: Fix Released Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: U
[Desktop-packages] [Bug 1121660] Re: No visual indication of automatic login
** Bug watch added: LightDM GTK+ Greeter Bugs #16 https://github.com/Xubuntu/lightdm-gtk-greeter/issues/16 ** Changed in: lightdm-gtk-greeter Importance: Undecided => Unknown ** Changed in: lightdm-gtk-greeter Status: New => Unknown ** Changed in: lightdm-gtk-greeter Remote watch: None => LightDM GTK+ Greeter Bugs #16 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1121660 Title: No visual indication of automatic login Status in LightDM GTK+ Greeter: Unknown Status in unity-greeter package in Ubuntu: Triaged Bug description: When automatically logging in there is no visual indication an autologin is about to occur and no way to cancel it. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1121660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1472143] Re: pause autologin-timeout when user active
** Bug watch added: LightDM GTK+ Greeter Bugs #39 https://github.com/Xubuntu/lightdm-gtk-greeter/issues/39 ** Changed in: lightdm-gtk-greeter Importance: Undecided => Unknown ** Changed in: lightdm-gtk-greeter Status: New => Unknown ** Changed in: lightdm-gtk-greeter Remote watch: None => LightDM GTK+ Greeter Bugs #39 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1472143 Title: pause autologin-timeout when user active Status in LightDM GTK+ Greeter: Unknown Status in unity-greeter package in Ubuntu: Confirmed Bug description: Xubuntu 15.04 lightdm 2.0.0-0ubuntu1 lightdm-gtk-greeter and unity-greeter autologin-user-timeout works, but doesn't take into account user activity. Timer should pause or reset ( i prefer reset ) when one user is trying to log into an other account than selected by autologin-user in order to avoid to log the user into a session he doesn't want to use. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1472143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1531224] Re: lightdm-gtk-greeter flickers once little after lightdm starts
** Bug watch added: LightDM GTK+ Greeter Bugs #46 https://github.com/Xubuntu/lightdm-gtk-greeter/issues/46 ** Changed in: lightdm-gtk-greeter Importance: Undecided => Unknown ** Changed in: lightdm-gtk-greeter Status: New => Unknown ** Changed in: lightdm-gtk-greeter Remote watch: None => LightDM GTK+ Greeter Bugs #46 -- 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/1531224 Title: lightdm-gtk-greeter flickers once little after lightdm starts Status in LightDM GTK+ Greeter: Unknown Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Bug context: · Arch Linux x86_64 4.3.3-2-ARCH · systemd 228-3 (using lightdm-plymouth.service) · plymouth 0.9.2-8 (compiled from AUR) · lightdm 1:1.16.6-2 · lightdm-gtk-greeter 1:2.0.1-2 At the end of boot process, right after plymouth splash, lightdm starts normally and the GTK+ greeter login screen is shown for about 1 second, but then the screen instantly flickers (goes black) and the greeter is redrawn. From here on, everything works flawlessly, but the brief flickering is certainly annoying. This happens every time and no other greeter I have tried presents this issue, so I can confirm it is lightdm-gtk-greeter-related. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1531224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
I've added this to the 20.04 development blueprint, so let's revisit and discuss. If we can't solve the problem with packaging, let's document the mini.iso installation process so others have an easier time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: Fix Released Status in xubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848766] Re: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator
Hey @doko, >From what I can tell, we're not shipping libappindicator at all in focal. Can you elaborate where this is coming from? http://cdimage.ubuntu.com/xubuntu/daily-live/current/focal-desktop- amd64.manifest -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1848766 Title: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator Status in libappindicator package in Ubuntu: New Status in pygtk package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator. We don't want to have Python2 anymore in seeds and images. So either xubuntu should stop using libappindicator, or libappindicator should provide Python3 packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1848766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848766] Re: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator
*** This bug is a duplicate of bug 1740637 *** https://bugs.launchpad.net/bugs/1740637 Thanks. jbicha referred to https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1740637 and mentioned that the python2 support is going to be dropped from libappindicator, so this should no longer be an issue for Xubuntu. Thanks for bringing it to my attention! ** Changed in: xubuntu-meta (Ubuntu) Status: New => Invalid ** Changed in: pygtk (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1740637 Remove python-appindicator and gir1.2-appindicator-0.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1848766 Title: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator Status in libappindicator package in Ubuntu: New Status in pygtk package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Invalid Bug description: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator. We don't want to have Python2 anymore in seeds and images. So either xubuntu should stop using libappindicator, or libappindicator should provide Python3 packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1848766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly
Assigned this issue to xubuntu-docs. Let's document the correct way to handle the installation of the xubuntu-desktop package, and make it easy for users to find (and forums to point to) when these questions arise in the future. ** Also affects: xubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Changed in: xubuntu-docs (Ubuntu) Status: New => Confirmed ** Changed in: xubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: apt install xubuntu-desktop does not resolve dependencies properly Status in apt package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in indicator-datetime package in Ubuntu: Invalid Status in xfce4-session package in Ubuntu: Fix Released Status in xubuntu-docs package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User
** Changed in: lightdm (Ubuntu) Status: New => Confirmed ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium -- 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/1874178 Title: Unlocking existing session needs two attempts after selecting Switch User Status in lightdm package in Ubuntu: Confirmed Bug description: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory
Also tagging snap since the issue is present on snaps that have run in
the user session.
** Also affects: snap (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/1828664
Title:
[snap] Broken link in theme directory
Status in gnome-characters package in Ubuntu:
Confirmed
Status in snap package in Ubuntu:
New
Bug description:
Reproduce steps
---
1. $ snap install gnome-characters communitheme
2. logoff and select communitheme session at the greeter (probably needs a
reload of GDM or reboot, I'm running the wayland session but it also happened
of X)
3. $ snap run gnome-characters
Affected snaps:
gnome-characters
gnome-calculator
gnome-logs
gnome-system-monitor
libreoffice
evince
gnome-contacts
eog
Symptoms
I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which
broke at some point about two month ago. Screenshots are here:
https://askubuntu.com/q/1142291/40581
I found that ~/snap/gnome-characters/current/themes is a broken link
even when removing the respective snap folder for the app, removing
and then reinstalling the gnome-characters snap. This has worked
before, please take a look at this.
In the meantime I fixed this with the following commands, according
the the error message:
rm ~/snap/gnome-characters/current/.themes
cp -av /snap/communitheme/current/share/themes
~/snap/gnome-characters/current/.themes
Version
---
```
$ snap info {gnome-characters,communitheme} | grep -vE
"^(summary|license|contact|description|commands):"
name: gnome-characters
publisher: Canonical*
Characters is a simple utility application to find and
insert unusual characters.
- gnome-characters
snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
tracking: stable
refresh-date: heute um 04:19 CEST
channels:
stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
beta: ^
edge: v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
installed: v3.32.1+git1.2050bba(258) 15MB -
---
name: communitheme
publisher: Didier Roche (didrocks)
Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
package allows you to try out the theme on Ubuntu 18.04 LTS.
To try out the theme, install this package on Ubuntu 18.04 LTS, restart
your computer and select the "Ubuntu with communitheme snap" session from
the login screen.
More information is available at
https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
snap-id: Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
tracking: stable
refresh-date: 59 days ago, at 17:46 CET
channels:
stable:0.1 2019-03-13 (1768) 16MB -
candidate: ^
beta: ^
edge: 0.1 2019-05-08 (1799) 17MB -
installed: 0.1(1768) 16MB -
```
---
Further investigation
-
I'm also seeing broken links on an 19.04 machine where I'm not using
the Communitheme snap but the preinstalled Yaru packages. I'm trying
out the dark theme but all snaps launch with Adwaita instead.
```
$ snap list
Name Version Rev Tracking Publisher
Notes
android-studio 3.4.0.1875stablesnapcrafters
classic
canonical-livepatch 9.3.0 77stablecanonical*
-
core 16-2.38.1 6818 stablecanonical*
core
core18 20190409941 stablecanonical*
base
gedit3.30.2+git14.bed83e929 89stablecanonical*
-
gnome-3-26-1604 3.26.0.20190228 82stable/… canonical*
-
gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 40stablecanonical*
-
gnome-calculator 3.32.1 406 stable/… canonical*
-
gnome-characters v3.32.1+git1.2050bba258 stablecanonical*
-
gnome-logs 3.32.0-4-ge8f3f37ca861stable/… canonical*
-
gtk-common-themes0.1-16-g2287c87 1198 stable/… canonical*
-
$ find snap/gnome-characters -xtype l
snap/gnome-characters/common/.cache/immodules/im-fcitx.so
snap/gnome-characters/common/.cache/immodules/im-wayland.so
snap/gnome-characters/common/.cache/immodules/im-broadway.so
snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
snap/gnome-characters/common/.cache/immodules/im-cedilla.so
snap/gnome-characters/common/.cache/immodules/im-ipa.so
snap/gnome-characters/common/.cache/immodules/im-xim.so
snap/gnome-characters/common/.cache/immodules/im-thai.so
sn
[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory
@John
Which component is responsible for linking
~/snap/packagename/current/.themes? Is this a per snap functionality or
snapd that would produce this? Currently it's broken for at least the
snaps listed in the description.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/1828664
Title:
[snap] Broken link in theme directory
Status in gnome-characters package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Invalid
Bug description:
Reproduce steps
---
1. $ snap install gnome-characters communitheme
2. logoff and select communitheme session at the greeter (probably needs a
reload of GDM or reboot, I'm running the wayland session but it also happened
of X)
3. $ snap run gnome-characters
Affected snaps:
gnome-characters
gnome-calculator
gnome-logs
gnome-system-monitor
libreoffice
evince
gnome-contacts
eog
Symptoms
I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which
broke at some point about two month ago. Screenshots are here:
https://askubuntu.com/q/1142291/40581
I found that ~/snap/gnome-characters/current/themes is a broken link
even when removing the respective snap folder for the app, removing
and then reinstalling the gnome-characters snap. This has worked
before, please take a look at this.
In the meantime I fixed this with the following commands, according
the the error message:
rm ~/snap/gnome-characters/current/.themes
cp -av /snap/communitheme/current/share/themes
~/snap/gnome-characters/current/.themes
Version
---
```
$ snap info {gnome-characters,communitheme} | grep -vE
"^(summary|license|contact|description|commands):"
name: gnome-characters
publisher: Canonical*
Characters is a simple utility application to find and
insert unusual characters.
- gnome-characters
snap-id: qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
tracking: stable
refresh-date: heute um 04:19 CEST
channels:
stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
beta: ^
edge: v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
installed: v3.32.1+git1.2050bba(258) 15MB -
---
name: communitheme
publisher: Didier Roche (didrocks)
Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
package allows you to try out the theme on Ubuntu 18.04 LTS.
To try out the theme, install this package on Ubuntu 18.04 LTS, restart
your computer and select the "Ubuntu with communitheme snap" session from
the login screen.
More information is available at
https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
snap-id: Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
tracking: stable
refresh-date: 59 days ago, at 17:46 CET
channels:
stable:0.1 2019-03-13 (1768) 16MB -
candidate: ^
beta: ^
edge: 0.1 2019-05-08 (1799) 17MB -
installed: 0.1(1768) 16MB -
```
---
Further investigation
-
I'm also seeing broken links on an 19.04 machine where I'm not using
the Communitheme snap but the preinstalled Yaru packages. I'm trying
out the dark theme but all snaps launch with Adwaita instead.
```
$ snap list
Name Version Rev Tracking Publisher
Notes
android-studio 3.4.0.1875stablesnapcrafters
classic
canonical-livepatch 9.3.0 77stablecanonical*
-
core 16-2.38.1 6818 stablecanonical*
core
core18 20190409941 stablecanonical*
base
gedit3.30.2+git14.bed83e929 89stablecanonical*
-
gnome-3-26-1604 3.26.0.20190228 82stable/… canonical*
-
gnome-3-28-1804 3.28.0-10-gaa70833.aa70833 40stablecanonical*
-
gnome-calculator 3.32.1 406 stable/… canonical*
-
gnome-characters v3.32.1+git1.2050bba258 stablecanonical*
-
gnome-logs 3.32.0-4-ge8f3f37ca861stable/… canonical*
-
gtk-common-themes0.1-16-g2287c87 1198 stable/… canonical*
-
$ find snap/gnome-characters -xtype l
snap/gnome-characters/common/.cache/immodules/im-fcitx.so
snap/gnome-characters/common/.cache/immodules/im-wayland.so
snap/gnome-characters/common/.cache/immodules/im-broadway.so
snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
snap/gnome-characters/common/.cache/immodules/im-cedilla.so
snap/gnome-characters/common/.cache/immodules/im-ipa.so
snap/gnome-characters/common/.cache/immodules/im-xim.s
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Branch linked: lp:~samuel-thibault/lightdm-gtk-greeter/at-spi-bus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Applied Samuel Thibault's patch to master, which seems like a safe solution benefiting the most users. ** Changed in: lightdm-gtk-greeter Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: Fix Committed Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580166] Re: Missing 'Save' icon for when there are changes to be saved
Xubuntu is using the libreoffice-style-elementay theme by default. ** Changed in: xubuntu-meta (Ubuntu) Status: New => Invalid -- 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/1580166 Title: Missing 'Save' icon for when there are changes to be saved Status in libreoffice package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: Invalid Bug description: Upon making a change to a file in LibreOffice (Writer/Calc/Impress/Draw/Math(/probably Base, not tested)), the 'Save' icon in the toolbar (which has 'Open' to the left of it and 'Export to PDF' to the right of it) changes to using the Galaxy theme icon for 'Save'. When an edit is made to a document and there are changes to be saved, there should be Human icon which is used for saving from the toolbar rather than Galaxy (which looks horribly inconsistent). I don't know if the problem is that a Human icon for 'saving when changes have been made since the last save' doesn't exist or if it hasn't been implemented correctly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-style-human 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: XFCE Date: Tue May 10 13:30:40 2016 InstallationDate: Installed on 2016-04-25 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1580166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
We've now had several reports of the latest package version in yakkety (2:2.99.917+git20160706-1ubuntu1) resolving this issue. Marking this bug as fixed. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Fix Released -- 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: Confirmed Status in X.Org X server: Confirmed Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: 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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
** Description changed: - Cursor is visible at unlock screen either after returning from suspend - or just locking. + [SRU for Ubuntu 16.04] + Package (yakkety): xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 + Current (xenial): xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 + + [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. + + [Debian Changelog (since 2:2.99.917+git20160325-1ubuntu1)] + xserver-xorg-video-intel (2:2.99.917+git20160706-1ubuntu1) yakkety; urgency=medium + * Merge from Debian. + + xserver-xorg-video-intel (2:2.99.917+git20160706-1) unstable; urgency=medium + * New upstream snapshot. + * fix-fd-leak-when-intel-scrn-create-fails.diff, sna-let-modesetting- + handle-gen9+.diff: Dropped as the fallback to modesetting will be + fully handled in the xserver. + * .docs: Include a minimal xorg.conf. + + xserver-xorg-video-intel (2:2.99.917+git20160522-1ubuntu1) yakkety; urgency=medium + * Merge from Debian. + * install-dri3info.diff: Install dri3info with the driver, add libxcomposite-dev + to build-depends. + + xserver-xorg-video-intel (2:2.99.917+git20160522-1) unstable; urgency=medium + * New upstream snapshot. (Closes: #823116) + * fix-fd-leak-when-intel-scrn-create-fails.diff: Fix a failure falling back + on another driver when scrn create fails. + + [Regression Potential] + Regression potential here seems minimal. However, as seen in the above Debian changelog, we have a new snapshot which includes several changes since March 25. + + === + + [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 -- 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: Confirmed Status in X.Org X server: Confirmed Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: [SRU for Ubuntu 16.04] Package (yakkety): xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 Current (xenial): xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 [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. [Debian Changelog (since 2:2.99.917+git20160325-1ubuntu1)] xserver-xorg-video-intel (2:2.99.917+git20160706-1ubuntu1) yakkety; urgency=medium
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Attaching debdiff: from xserver-xorg-video-intel_2.99.917+git20160325-1ubuntu1 toxserver-xorg-video-intel_2.99.917+git20160706-1ubuntu1 ** Patch added: "Debdiff for yakkety to xenail backport" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1568604/+attachment/4700756/+files/xserver-xorg-video-intel_2.99.917+git20160706-1ubuntu1~16.04.debdiff -- 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: Confirmed Status in X.Org X server: Confirmed Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Confirmed Bug description: [SRU for Ubuntu 16.04] Package (yakkety): xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 Current (xenial): xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 [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. [Debian Changelog (since 2:2.99.917+git20160325-1ubuntu1)] xserver-xorg-video-intel (2:2.99.917+git20160706-1ubuntu1) yakkety; urgency=medium * Merge from Debian. xserver-xorg-video-intel (2:2.99.917+git20160706-1) unstable; urgency=medium * New upstream snapshot. * fix-fd-leak-when-intel-scrn-create-fails.diff, sna-let-modesetting- handle-gen9+.diff: Dropped as the fallback to modesetting will be fully handled in the xserver. * .docs: Include a minimal xorg.conf. xserver-xorg-video-intel (2:2.99.917+git20160522-1ubuntu1) yakkety; urgency=medium * Merge from Debian. * install-dri3info.diff: Install dri3info with the driver, add libxcomposite-dev to build-depends. xserver-xorg-video-intel (2:2.99.917+git20160522-1) unstable; urgency=medium * New upstream snapshot. (Closes: #823116) * fix-fd-leak-when-intel-scrn-create-fails.diff: Fix a failure falling back on another driver when scrn create fails. [Regression Potential] Regression potential here seems minimal. However, as seen in the above Debian changelog, we have a new snapshot which includes several changes since March 25. === [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 1713344] Re: gnome-software core dump
** Package changed: xfce4-terminal (Ubuntu) => gnome-software (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/1713344 Title: gnome-software core dump Status in gnome-software package in Ubuntu: New Bug description: gnome software core dumped @Leftwing-nonextremist:~$ gnome-software %U Segmentation fault (core dumped) software would open. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xfce4-terminal 0.8.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: XFCE Date: Mon Aug 28 00:55:49 2017 ExecutablePath: /usr/bin/xfce4-terminal InstallationDate: Installed on 2017-08-19 (8 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-terminal UpgradeStatus: Upgraded to artful on 2017-08-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1713344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Summary changed: - Accessibility partly broken due to X root window being kept from login session. + [PATCH] Accessibility partly broken due to X root window being kept from login session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Xfce still needs -synaptics, addressed with http://bazaar.launchpad.net /~xubuntu-dev/ubuntu-seeds/xubuntu.artful/revision/1015 ** Also affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in xorg package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: New Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Sett
This does not affect a base install of Xubuntu, but one that is shared with other installed sessions that pull in the GNOME Control Center and the Date Time Indicator. The GNOME Control Center only displays it's configuration tools inside of a GNOME or GNOME-like environment, and will just show up blank anywhere else. To populate these settings, just launch the control center with the below command. env XDG_CURRENT_DESKTOP=GNOME gnome-control-center Moving this bug to indicator-datetime since it could be made aware of the running desktop and gnome-control-center since it seems to be an intentional functionality of the GNOME desktop. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** No longer affects: xubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settings) Status in gnome-control-center package in Ubuntu: New Status in indicator-datetime package in Ubuntu: New Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760078] Re: Double login required from suspend
Not seeing this currently. I have seen this in the past when VT switching from the lock screen. -- 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/1760078 Title: Double login required from suspend Status in lightdm package in Ubuntu: New Bug description: Following a suspend. Get unlock screen - which then gets me a desktop. Returned to unlock screen to enter password a second time. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 12:09:46 2018 InstallationDate: Installed on 2018-03-08 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760073] Re: No network from suspend resume
Not seeing this on my machine, so it may be kernel related. ** Also affects: linux (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/1760073 Title: No network from suspend resume Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Following a resume from suspend - no network available on machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:53:22 2018 InstallationDate: Installed on 2018-03-08 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate servic
Turned up the importance for this bug. For a user, a 75-second wait time when they are used to 0-10 would be an indication there is a serious bug and the software (Xubuntu, Ubuntu MATE, and anything else yet unidentified) does not run on their system. ** Changed in: bluez (Ubuntu) Importance: Undecided => Critical -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate servic
Since it seemed like this issue was coming from bluez or blueman, I did some package removal tests and was surprised by the results. These were done in order, which all packages removed in the previous step still removed in the following step. 1. Remove pulseaudio-module-bluetooth, no change. 2. Remove blueman, no change. 3. Remove bluez, bluez-cups, bluez-obexd, no change. 4. Autoremoved libbluetooth3 (brltty brltty-x11 libbluetooth3 network-manager network-manager-gnome network-manager-pptp network-manager-pptp-gnome), and still no change. -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate servic
If this bug does not affect Ubuntu directly, this is a list of shared differences that Ubuntu MATE and Xubuntu have with Ubuntu. Hopefully this can help identify where the issue exists. ** Attachment added: "Differences with Ubuntu" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5099620/+files/ubuntu_vs_mate_and_xubuntu.txt -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818395] [NEW] Please demote lightdm greeter recommends to suggests
Public bug reported: Please see https://bugs.launchpad.net/ubuntu/+source/indicator- datetime/+bug/1754872/comments/25 for some background on this bug report. I'd like to request that the lightdm greeter Recommends... unity-greeter | lightdm-greeter (virtual package) | lightdm-kde-greeter be moved to Suggests. It seems the apt installation order causes unity- greeter (and other unity components) to be installed along with lightdm- gtk-greeter when installing the xubuntu-desktop task. Since each of the lightdm greeters should depend on lightdm, I think this change helps make greeter installation more explicit and should prevent the installation of multiple greeters when only one is needed or requested. ** 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/1818395 Title: Please demote lightdm greeter recommends to suggests Status in lightdm package in Ubuntu: New Bug description: Please see https://bugs.launchpad.net/ubuntu/+source/indicator- datetime/+bug/1754872/comments/25 for some background on this bug report. I'd like to request that the lightdm greeter Recommends... unity-greeter | lightdm-greeter (virtual package) | lightdm-kde-greeter be moved to Suggests. It seems the apt installation order causes unity-greeter (and other unity components) to be installed along with lightdm-gtk-greeter when installing the xubuntu-desktop task. Since each of the lightdm greeters should depend on lightdm, I think this change helps make greeter installation more explicit and should prevent the installation of multiple greeters when only one is needed or requested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1818395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
The new upstream url for the Xorg bug is https://gitlab.freedesktop.org/xorg/xserver/issues/577 ** Also affects: greybird-gtk-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server Importance: Medium => Undecided ** Changed in: xorg-server Status: Unknown => New ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #92681 => None ** Also affects: xfce4-panel (Ubuntu Disco) Importance: Undecided Assignee: Simon Steinbeiß (ochosi) Status: Confirmed ** Also affects: xorg-server (Ubuntu Disco) Importance: Undecided Status: Confirmed ** Also affects: greybird-gtk-theme (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: xfce4-panel (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: greybird-gtk-theme (Ubuntu Cosmic) Importance: Undecided Status: New -- 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/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: New Status in greybird-gtk-theme package in Ubuntu: New Status in xfce4-panel package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in greybird-gtk-theme source package in Cosmic: New Status in xfce4-panel source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in greybird-gtk-theme source package in Disco: New Status in xfce4-panel source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
This issue is resolved with greybird 3.22.10-1 and xfce4-panel 4.13.4-1 ** Changed in: greybird-gtk-theme (Ubuntu Disco) Status: New => Fix Released -- 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/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: New Status in greybird-gtk-theme package in Ubuntu: Fix Released Status in xfce4-panel package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in greybird-gtk-theme source package in Cosmic: Triaged Status in xfce4-panel source package in Cosmic: Triaged Status in xorg-server source package in Cosmic: New Status in greybird-gtk-theme source package in Disco: Fix Released Status in xfce4-panel source package in Disco: Fix Released Status in xorg-server source package in Disco: Confirmed Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
This issue is resolved with greybird 3.22.10-1 and xfce4-panel 4.13.4-1 ** Changed in: xfce4-panel (Ubuntu Disco) Status: Confirmed => Fix Released ** Changed in: greybird-gtk-theme (Ubuntu Cosmic) Status: New => Triaged ** Changed in: greybird-gtk-theme (Ubuntu Cosmic) Assignee: (unassigned) => Sean Davis (bluesabre) ** Changed in: xfce4-panel (Ubuntu Cosmic) Status: New => Triaged ** Changed in: xfce4-panel (Ubuntu Cosmic) Assignee: (unassigned) => Sean Davis (bluesabre) -- 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/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: New Status in greybird-gtk-theme package in Ubuntu: Fix Released Status in xfce4-panel package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in greybird-gtk-theme source package in Cosmic: Triaged Status in xfce4-panel source package in Cosmic: Triaged Status in xorg-server source package in Cosmic: New Status in greybird-gtk-theme source package in Disco: Fix Released Status in xfce4-panel source package in Disco: Fix Released Status in xorg-server source package in Disco: Confirmed Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager
Fix applied in the below commit. https://git.launchpad.net/xubuntu-default- settings/commit/?id=3cd679e4c3d5efeb0e6d21027e072554037b244f ** Changed in: xubuntu-default-settings (Ubuntu) Status: Confirmed => Triaged ** Changed in: xubuntu-default-settings (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in exo: Confirmed Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Fix Committed Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1778069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1548647] Re: LibreOffice uses breeze style
This is partly related to the fact that the libreoffice-gtk recommends libreoffice-style-breeze | libreoffice-style-tango One of Xubuntu 16.04's release goals is to ship only a single theme. We have attempted this in the past with this bug report: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1483914 Now that the libreoffice-style-elementary theme is built with the libreoffice package, we'd like to propose libreoffice-style-elementary as an alternate recommends. I have attached a debdiff which should resolve this issue. I am also marking libreoffice as an affected project. Please let me know if there are any questions or concerns. ** Patch added: "debdiff for libreoffice-style-elementary" https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1548647/+attachment/4588287/+files/elementary.debdiff ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1548647 Title: LibreOffice uses breeze style Status in One Hundred Papercuts: Confirmed Status in libreoffice package in Ubuntu: New Status in xubuntu-artwork package in Ubuntu: Confirmed Bug description: LO in Xubuntu should be using Elementary theme as default - set to Breeze (and on live session) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xubuntu-artwork 15.12.2 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CurrentDesktop: XFCE Date: Tue Feb 23 07:11:10 2016 LiveMediaBuild: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160222.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xubuntu-artwork UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1548647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
