[Bug 1350871] Re: location service is waking up at 10Hz causing possible unwanted wakeups
** Tags added: phablet -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1350871 Title: location service is waking up at 10Hz causing possible unwanted wakeups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1350871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1397156] Re: Use Bluez 5
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1397156 Title: Use Bluez 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1397156/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1474182] Re: Mystery keyring password prompts pop up for no reason
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1474182 Title: Mystery keyring password prompts pop up for no reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1474182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1474182] Re: Mystery keyring password prompts pop up for no reason
I am also seeing this (on 15.04), it started happening a few weeks ago. As suggested above it is associated with oneconf. Immediately before the popup appears (or as it appears) data in .cache/oneconf//package_list_... and host are updated and after a valid pwd is entered last_sync is updated. In auth.log the following is seen after entering the pwd Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: completed password prompt for callback :1.96@/org/gnome/keyring/Prompt/p1 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: encrypting data Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: sending the secret exchange: [sx-aes-1]\npublic=[snipped] Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: closing the prompt Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p1@:1.96 Aug 31 07:54:40 tigger gcr-prompter[]: Gcr: calling the PromptDone on /org/gnome/keyring/Prompt/p1@:1.96, and ignoring reply Aug 31 07:54:50 tigger gcr-prompter[]: 10 second inactivity timeout, quitting Aug 31 07:54:50 tigger gcr-prompter[]: Gcr: unregistering prompter Aug 31 07:54:50 tigger gcr-prompter[]: Gcr: disposing prompter Aug 31 07:54:50 tigger gcr-prompter[]: Gcr: finalizing prompter -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1474182 Title: Mystery keyring password prompts pop up for no reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1474182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1474182] Re: Mystery keyring password prompts pop up for no reason
** Changed in: gnome-session (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1474182 Title: Mystery keyring password prompts pop up for no reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1474182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1391917] Re: gnome-system-monitor is obsolete
** Description changed: The version distributed with Ubuntu 14.04 is 3.8.2.1. Versions older than 3.14 are not supported and considered obsolete by upstream. Cf. bug GNOME #740021 + + [Impact] + The documentation bundled does not match the application. The documentation shows a screen shot with Edit menu but there is no Edit menu in the application. The documentation has been fixed by upstream. + + [Test case] + Tell GNOME System Monitor to show help. Look at the section "When You Start System Monitor" in the chapter "Getting Started". Look at the screen shot with the Edit menu. Return to GNOME System Monitor and observe that there is no Edit menu. + + [Regression Potential] + If the application fails in Ubuntu, the users will find it difficult to manage the processes on their system, to identify, pause and diagnose their resource usage. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1391917 Title: gnome-system-monitor is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1391917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1490781] [NEW] Add a button to permantently get next random image
Public bug reported: Currently it's only possible to get the next random image with the menuitem or the keyboard shortcut Ctrl+M. It'd be nice to have a trigger button which changes the function of the next image button to get the next random image and the go back button to get the last shown image. It's not so nice to have to click twice to achieve that with the menu item. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: eog 3.14.4-1 Uname: Linux 4.1.4-040104-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 1 02:30:00 2015 InstallationDate: Installed on 2015-06-08 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: eog UpgradeStatus: Upgraded to vivid on 2015-06-09 (83 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid ** Description changed: Currently it's only possible to get the next random image with the menuitem or the keyboard shortcut Ctrl+M. It'd be nice to have a trigger button which changes the function of the next image button to get the next random image and the go back button to get - the last shown image. + the last shown image. It's a bit annoying to have to click twice to + achieve that with the menu item. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: eog 3.14.4-1 Uname: Linux 4.1.4-040104-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 1 02:30:00 2015 InstallationDate: Installed on 2015-06-08 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: eog UpgradeStatus: Upgraded to vivid on 2015-06-09 (83 days ago) ** Description changed: Currently it's only possible to get the next random image with the menuitem or the keyboard shortcut Ctrl+M. It'd be nice to have a trigger button which changes the function of the next image button to get the next random image and the go back button to get - the last shown image. It's a bit annoying to have to click twice to - achieve that with the menu item. + the last shown image. It's not so nice to have to click twice to achieve + that with the menu item. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: eog 3.14.4-1 Uname: Linux 4.1.4-040104-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 1 02:30:00 2015 InstallationDate: Installed on 2015-06-08 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: eog UpgradeStatus: Upgraded to vivid on 2015-06-09 (83 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1490781 Title: Add a button to permantently get next random image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1490781/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1490442] [NEW] nautilus crashes when i change wallpaper
Public bug reported: nautilus crashes when i change a few wallpaper or just one. Nemo is also falls. Sorry for bad English. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9.1 [modified: usr/share/applications/nautilus-folder-handler.desktop usr/share/applications/nautilus-home.desktop usr/share/applications/nautilus.desktop usr/share/applications/org.gnome.Nautilus.desktop] ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5 Uname: Linux 3.19.0-27-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 31 13:44:45 2015 InstallationDate: Installed on 2013-05-08 (844 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [deleted] ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1490442 Title: nautilus crashes when i change wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1490442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
This problem still exists in trusty. after suspend / resume an external excrypted harddrive automaint fails with this error. How to solve this totally annoying behaviour? Also I would like to know: how can I make the automount mechanism forget the password? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/484429 Title: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1487471] Re: Udev rule for MTP with nvidia Shield
** Package changed: systemd (Ubuntu) => libmtp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1487471 Title: Udev rule for MTP with nvidia Shield To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1487471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1451924] Re: gnome-terminal's VteTerminal doesn't have overlay scrollbars
They do for me?! However, they're hardly usable because they don't expand on hover. (I think that's because vte doesn't use GtkScrolledWindow.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1451924 Title: gnome-terminal's VteTerminal doesn't have overlay scrollbars To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1451924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1484027] Re: systemd-tmpfiles-clean warns about duplicate /var/log line
There's nothing to fix, it's just a harmless warning as rsyslog drops in its own configuration file. ** Summary changed: - systemd-tmpfiles-clean reports warning in logs + systemd-tmpfiles-clean warns about duplicate /var/log line ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1484027 Title: systemd-tmpfiles-clean warns about duplicate /var/log line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1484027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
Marking this as "Fix released" for glib and LibreOffice in Ubuntu as there are Ubuntu releases where this is fixed. A SRU for Ubuntu 12.04 would need a series target. But that is theoretical as the amount of rebuilds needed for that are way too high risk and it will get closed WontFix anyway. ** Changed in: gvfs (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1484027] Re: systemd-tmpfiles-clean warns about duplicate /var/log line
Reopened, but if anything this is more a problem with logcheck (or perhaps just missing ignore patterns). systemd's journal keeps the priority of a message, and logcheck should certainly only look at >= warning? ** Changed in: systemd (Ubuntu) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1484027 Title: systemd-tmpfiles-clean warns about duplicate /var/log line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1484027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1476256] Re: /lib/systemd/systemd-journald:6:log_assert_failed:device_get_id_filename:device_read_db_aux:device_read_db:sd_device_get_devlink_first
Fixed in version 223 (in wily), thus closing. ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1476256 Title: /lib/systemd/systemd- journald:6:log_assert_failed:device_get_id_filename:device_read_db_aux:device_read_db:sd_device_get_devlink_first To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1476256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1476364] Re: “systemd --user” instance can't find d-bus
Switching user with "su" does not count as opening a full new session (see /etc/pam.d/su). This does not start a session bus and systemd process in particular. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1476364 Title: “systemd --user” instance can't find d-bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1476364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1490593] [NEW] gnome-terminal forks even with `--disable-factory`
Public bug reported: Manual states: --disable-factory Do not register with the activation name server, do not re-use an active terminal. Yet terminal opens and "foo" is being printed immediately even though the terminal didn't close: $ gnome-terminal --disable-factory; echo foo foo ``` This behavior was different in the past and doesn't seem "normal" for a Linux application, e.g. it now prevents using gnome-terminal as a `vim` wrapper for an external editor. Usually Linux applications are manually forked with ampersand and as far as I understand it still should be possible with a `--disable-factory` argument. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 31 16:11:37 2015 InstallationDate: Installed on 2014-02-06 (571 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131219) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to vivid on 2015-04-30 (122 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Description changed: Manual states: - ``` - $ man gnome-terminal | grep -a1 factory | tail -n2 ---disable-factory - Do not register with the activation name server, do not re-use an active terminal. - ``` - Yet terminal opens and "foo" is being printed immediately. - ``` + --disable-factory + Do not register with the activation name server, do not re-use an + active terminal. + + + Yet terminal opens and "foo" is being printed immediately even though the terminal didn't close: + $ gnome-terminal --disable-factory; echo foo foo ``` - This behavior was different in the past as confirmed on several websites - and doesn't seem "normal" for a Linux application, e.g. it now prevents - using gnome-terminal as `vim` wrapper. Usually Linux applications are - manually forked with ampersand and as far as I understand it still - should be possible with a `--disable-factory` argument. + This behavior was different in the past and doesn't seem "normal" for a + Linux application, e.g. it now prevents using gnome-terminal as a `vim` + wrapper for an external editor. Usually Linux applications are manually + forked with ampersand and as far as I understand it still should be + possible with a `--disable-factory` argument. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 31 16:11:37 2015 InstallationDate: Installed on 2014-02-06 (571 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20131219) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to vivid on 2015-04-30 (122 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1490593 Title: gnome-terminal forks even with `--disable-factory` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1490593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1470399] Re: udev duplicates entries in 70-persistent-net.rules
This got fixed in 219-6, and thus in 15.04. ** Package changed: udev (Ubuntu) => systemd (Ubuntu) ** Bug watch added: Debian Bug tracker #765577 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765577 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1470399 Title: udev duplicates entries in 70-persistent-net.rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1470399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1170164] Re: can't switch input method at all
I have the very same issue but I don't think it's gnome-terminal related. Please confirm restarting gnome itself doesn't help (as in: alt+F2, type in letter "r" and press enter, you have to alt+tab twice afterwards to regain focus on terminal), we will be sure then it really is a gnome-terminal and not gnome issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1170164 Title: can't switch input method at all To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1170164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1451924] Re: gnome-terminal's VteTerminal doesn't have overlay scrollbars
On Mon, Aug 31, 2015 at 08:43:09AM -, Lars Uebernickel wrote: > They do for me?! However, they're hardly usable because they don't > expand on hover. (I think that's because vte doesn't use > GtkScrolledWindow.) Isn't it that they have the styling from the theme but not the behaviour? They don't seem to be /overlay/ for me; the content reflows if I expand them. (I guess because it handles those itself, as you say.) With our latest theme the behaviour seems better than I recall from before though. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1451924 Title: gnome-terminal's VteTerminal doesn't have overlay scrollbars To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1451924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 484429] Re: Plugging in a LUKS device causes the following error: Error unlocking device: cryptsetup exited with exit code 239: Command failed: Device already exists
BTW this error seems to be triggered by the password input mechanism -
when I save the luks password "forever", volume management will always
remount that enrypted device without trouble after resume.
The two other options ("forget immediately" and "forget when log out")
lead to the described problem with cryptsetup failing with a "device
already exists".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/484429
Title:
Plugging in a LUKS device causes the following error: Error unlocking
device: cryptsetup exited with exit code 239: Command failed: Device
already exists
To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/484429/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1470399] [NEW] udev duplicates entries in 70-persistent-net.rules
You have been subscribed to a public bug:
After a fresh installation of 14.04, I had various troubles with the ethernet
NIC. Long story short, there were duplicate entries in
/etc/udev/rules.d/70-persistent-net.rules .
The 70-persistent-net.rules file has 5 entries for a 4 port NIC (Broadcom
Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe).
-
# PCI device 0x14e4:0x165f (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="54:9f:35:09:8f:69", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth1"
# PCI device 0x14e4:0x165f (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="54:9f:35:09:8f:6b", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth3"
# PCI device 0x14e4:0x165f (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="54:9f:35:09:8f:68", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
# PCI device 0x14e4:0x165f (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="54:9f:35:09:8f:6a", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth2"
# this last declaration was generated by udev but overrides prior command
with same ATTR{address} value.
# PCI device 0x14e4:0x165f (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="54:9f:35:09:8f:68", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth4"
-
lspci shows only 4 PCI devices.
-
$ lspci -vn | grep -A 16 -F '14e4:165f'
01:00.0 0200: 14e4:165f
Subsystem: 1028:1f5b
Flags: bus master, fast devsel, latency 0, IRQ 41
Memory at 91b3 (64-bit, prefetchable) [size=64K]
Memory at 91b4 (64-bit, prefetchable) [size=64K]
Memory at 91b5 (64-bit, prefetchable) [size=64K]
Expansion ROM at 91b8 [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable+ Count=17 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 00-00-54-9f-35-09-8f-68
Capabilities: [150] Power Budgeting
Capabilities: [160] Virtual Channel
Kernel driver in use: tg3
--
01:00.1 0200: 14e4:165f
Subsystem: 1028:1f5b
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at 91b0 (64-bit, prefetchable) [size=64K]
Memory at 91b1 (64-bit, prefetchable) [size=64K]
Memory at 91b2 (64-bit, prefetchable) [size=64K]
Expansion ROM at 91bc [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 00-00-54-9f-35-09-8f-69
Capabilities: [150] Power Budgeting
Capabilities: [160] Virtual Channel
Kernel driver in use: tg3
--
02:00.0 0200: 14e4:165f
Subsystem: 1028:1f5b
Flags: bus master, fast devsel, latency 0, IRQ 40
Memory at 91a3 (64-bit, prefetchable) [size=64K]
Memory at 91a4 (64-bit, prefetchable) [size=64K]
Memory at 91a5 (64-bit, prefetchable) [size=64K]
Expansion ROM at 91a8 [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number 00-00-54-9f-35-09-8f-6a
Capabilities: [150] Power Budgeting
Capabilities: [160] Virtual Channel
Kernel driver in use: tg3
--
02:00.1 0200: 14e4:165f
Subsystem: 1028:1f5b
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at 91a0 (64-bit, prefetchable) [size=64K]
Memory at 91a1 (64-bit, prefetchable) [size=64K]
Memory at 91a2 (64-bit, prefetchable) [size=64K]
Expansion ROM at 91ac [disabled] [size=256K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable-
[Bug 1488954] Re: systemctl is-active udev returns unknown
** Package changed: udev (Ubuntu) => systemd (Ubuntu) ** No longer affects: systemd (Ubuntu) ** Project changed: systemd => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Summary changed: - systemctl is-active udev returns unknown + systemctl is-active on aliased names returns unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1488954 Title: systemctl is-active on aliased names returns unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1488954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1478204] Re: ACPI 219 -> boot failure
There isn't anything to go with here. It seems independent of the init system, and mostly related to the graphics driver, i. e. a kernel issue. Can you please "e"dit the default boot entry in grub and drop the "quiet"? Please make/attach a screenshot (with a camera) when it freezes. Thanks! ** Package changed: systemd (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1478204 Title: ACPI 219 -> boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1478204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1481435] Re: package systemd 219-7ubuntu6 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned
Removing systemd (219-7ubuntu6) ... systemd is the active init system, please switch to another before removing systemd. Err, yes. Don't do that then :-) ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1481435 Title: package systemd 219-7ubuntu6 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1481435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
This sounds similar to bug 1270257, but that was closed due to getting too much noise. ** Package changed: dbus (Ubuntu) => network-manager (Ubuntu) ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1468624] [NEW] job queue not populated and nothing listed
You have been subscribed to a public bug: when a printing task is started, it happens that some old jobs are still in job queue and so are printed first instead of the wanted one. Opening the hplip toolbox, the old jobs are not listed, so its impossible to know about it/them and their numbers. And there is no option to blindly emptying that queue. Such working feature is really needed. But if the user ask for opening a task into that hplip toolbox, that time the job is displayed with its path. That is expected, but the real pain is about these old jobs not listed, not shown and fully unknown. On the other side cups is also fully ignoring to list & display these old jobs: this is also fully awaited. https://github.com/gtkd-developers/GtkD/issues/126 https://bugzilla.gnome.org/show_bug.cgi?id=754346 https://bugs.launchpad.net/hplip/+bug/1490273 Tray icon missing ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: hplip 3.15.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.0.0-3.5-generic 4.0.5 Uname: Linux 4.0.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17.3-0ubuntu4 Architecture: i386 CupsErrorLog: CurrentDesktop: GNOME Date: Thu Jun 25 08:29:24 2015 Lpstat: device for Photosmart-C4500-series: usb://HP/Photosmart%20C4500%20series?serial=CN87JD4109057K=1 device for Photosmart_C4500: hp:/usb/Photosmart_C4500_series?serial=CN87JD4109057K Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Photosmart_C4500.ppd', '/etc/cups/ppd/Photosmart-C4500-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Photosmart_C4500.ppd: Permission denied grep: /etc/cups/ppd/Photosmart-C4500-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-3-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: hplip UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily -- job queue not populated and nothing listed https://bugs.launchpad.net/bugs/1468624 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1468624] Re: job queue not populated and nothing listed
Closing, the two issues were properly reported upstream now. ** Project changed: cups => cups (Ubuntu) ** Package changed: cups (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: New => Invalid ** Changed in: hplip (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1468624 Title: job queue not populated and nothing listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1468624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1475989] Re: package libpam-systemd:amd64 204-5ubuntu20.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
This means that pam-auth-update crashed with signal 11 (i. e. SIGSEGV). ** Package changed: systemd (Ubuntu) => pam (Ubuntu) ** Summary changed: - package libpam-systemd:amd64 204-5ubuntu20.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 + pam-auth-update crashes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1475989 Title: pam-auth-update crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1475989/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1488954] [NEW] systemctl is-active udev returns unknown
You have been subscribed to a public bug: There is a symlink in /lib/systemd/system from udev.service to systemd- udevd.service, however, running "systemctl is-active udev" returns "unknown" instead of "active" initially. This can be solved by running "systemctl status udev" once, but for monitoring the service it would be nicer if the "is-active" would be working out of the box. $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy udev udev: Installed: 219-7ubuntu6 Candidate: 219-7ubuntu6 Version table: *** 219-7ubuntu6 0 500 http://eu.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 219-7ubuntu3 0 500 http://eu.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ** Affects: systemd Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- systemctl is-active udev returns unknown https://bugs.launchpad.net/bugs/1488954 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1488954] [NEW] systemctl is-active udev returns unknown
You have been subscribed to a public bug: There is a symlink in /lib/systemd/system from udev.service to systemd- udevd.service, however, running "systemctl is-active udev" returns "unknown" instead of "active" initially. This can be solved by running "systemctl status udev" once, but for monitoring the service it would be nicer if the "is-active" would be working out of the box. $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy udev udev: Installed: 219-7ubuntu6 Candidate: 219-7ubuntu6 Version table: *** 219-7ubuntu6 0 500 http://eu.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 219-7ubuntu3 0 500 http://eu.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- systemctl is-active udev returns unknown https://bugs.launchpad.net/bugs/1488954 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
