[Desktop-packages] [Bug 1921497] [NEW] xdg-settings set default-url-scheme-handler changes the entry for mime type text/html

2021-03-26 Thread berkes
Public bug reported:

>From https://github.com/telegramdesktop/tdesktop/issues/16051

Reproduce:

1. Ensure that `text/html` in *$HOME/.config/mimeapps.list* is set to a known 
value, e.g. firefox.desktop.
2. Create a .desktop file named *telegram-desktop_telegram-desktop.desktop*. 
See below for an example file.
3. run `xdg-settings set default-url-scheme-handler tg 
telegram-desktop_telegram-desktop.desktop`
4. Now `xdg-open` or `gio open` will open any HTML file not in firefox, but 
with telegram.
5. in *$HOME/.config/mimeapps.list* the entry for `text/html` is changed to 
`text/html=telegram-desktop_telegram-desktop.desktop`.

Expected behaviour: 
HTML files are opened in firefox or the app defined before.

Actual behaviour:
HTML files are opened in Telegram (which cannot handle this).

telegram-desktop is an example, and is how I experienced this issue. I'm
not familiar enough with scheme-handlers and xdg-utils to be able to
boil down a desktop-file to the bare minimals to reproduce this. Sorry
for that.


*telegram-desktop_telegram-desktop.desktop* contents:
```
[Desktop Entry]
X-SnapInstanceName=telegram-desktop
Version=1.0
Name=Telegram Desktop
Comment=Official desktop version of Telegram messaging app
Exec=env 
BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/telegram-desktop_telegram-desktop.desktop
 /snap/bin/telegram-desktop -- %u
Icon=/snap/telegram-desktop/2551/meta/gui/icon.png
Terminal=false
StartupWMClass=TelegramDesktop
Type=Application
Categories=Chat;Network;InstantMessaging;Qt;
MimeType=x-scheme-handler/tg;
Keywords=tg;chat;im;messaging;messenger;sms;tdesktop;
```

I've gotten this file by installing telegram with snap and it is then
located at */var/lib/snapd/desktop/applications/telegram-
desktop_telegram-desktop.desktop*. I'm not sure if the desktop file
works as it references to snap directories that do not exist if
telegram-desktop is not installed.

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1921497

Title:
  xdg-settings set default-url-scheme-handler changes the entry for mime
  type text/html

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  From https://github.com/telegramdesktop/tdesktop/issues/16051

  Reproduce:

  1. Ensure that `text/html` in *$HOME/.config/mimeapps.list* is set to a known 
value, e.g. firefox.desktop.
  2. Create a .desktop file named *telegram-desktop_telegram-desktop.desktop*. 
See below for an example file.
  3. run `xdg-settings set default-url-scheme-handler tg 
telegram-desktop_telegram-desktop.desktop`
  4. Now `xdg-open` or `gio open` will open any HTML file not in firefox, but 
with telegram.
  5. in *$HOME/.config/mimeapps.list* the entry for `text/html` is changed to 
`text/html=telegram-desktop_telegram-desktop.desktop`.

  Expected behaviour: 
  HTML files are opened in firefox or the app defined before.

  Actual behaviour:
  HTML files are opened in Telegram (which cannot handle this).

  telegram-desktop is an example, and is how I experienced this issue.
  I'm not familiar enough with scheme-handlers and xdg-utils to be able
  to boil down a desktop-file to the bare minimals to reproduce this.
  Sorry for that.

  
  *telegram-desktop_telegram-desktop.desktop* contents:
  ```
  [Desktop Entry]
  X-SnapInstanceName=telegram-desktop
  Version=1.0
  Name=Telegram Desktop
  Comment=Official desktop version of Telegram messaging app
  Exec=env 
BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/telegram-desktop_telegram-desktop.desktop
 /snap/bin/telegram-desktop -- %u
  Icon=/snap/telegram-desktop/2551/meta/gui/icon.png
  Terminal=false
  StartupWMClass=TelegramDesktop
  Type=Application
  Categories=Chat;Network;InstantMessaging;Qt;
  MimeType=x-scheme-handler/tg;
  Keywords=tg;chat;im;messaging;messenger;sms;tdesktop;
  ```

  I've gotten this file by installing telegram with snap and it is then
  located at */var/lib/snapd/desktop/applications/telegram-
  desktop_telegram-desktop.desktop*. I'm not sure if the desktop file
  works as it references to snap directories that do not exist if
  telegram-desktop is not installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1921497/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

2020-05-04 Thread berkes
The issues with dependant scripts like chromerunner are not solved
either.

Were external scripts considered when building this "solution" at all?
External scripts, running chromium, obviously, want the process they
spawn to exit -including any children that that process might spawn-.

Breaking this, is bad.

If, for some reason, different launch-patterns are required, such as
update processes, CLI-processes, scripts or user-interaction, could we
not introduce *standalone* scripts for that?

E.g. "update-chromium.sh" that would do all the 
hackish-run-in-background-with-sleep. And avoid cluttering the generic runner 
with that? 
Or, if that *has* to be included in the generic launching, can we then 
introduce a `chromium-cli` or somesuch that does *not* have all these hacks for 
during updates in place?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1864901

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running

2020-04-20 Thread berkes
It also occurs with a freshly installed chromium.

It can be easily reproduced:

```
$ pgrep chromium | xargs kill # kill any running chromium (beware!)
$ pgrep chromium | wc -l
0 # There are non running
$ /snap/bin/chromium --product-version # command quits immediately.
$ pgrep chromium | wc -l
1
$ /snap/bin/chromium # opens a browser.
# Quit browser manually.
$ pgrep chromium | wc -l
2
$ ps faux | grep chromium # check any processes running.
\_/bin/sh /snap/chromium/1100/bin/chromium.launcher --product-version
\_/bin/sh /snap/chromium/1100/bin/chromium.launcher
```

This shows that a process remains active after closing or running.
The `ps faux` shows the leftover running processes and clearly shows they no 
longer have a parent: it seems the parent process forks, then quits, but leaves 
its child running.

Above comment comes from a bug that this behaviour introduced in a
project that uses chrome:
https://github.com/titusfortner/webdrivers/issues/168

So, besides it leaving around running processes (slightly messy), it
causes bugs (hanging) in scripts and tools that wait for chrome+children
to exit.


** Bug watch added: github.com/titusfortner/webdrivers/issues #168
   https://github.com/titusfortner/webdrivers/issues/168

-- 
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/1864901

Title:
  [snap] suggestion: alert users when the snap has been refreshed while
  running

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  When the chromium snap is being automatically refreshed to a newer
  revision while the app is running, undefined behaviour might happen,
  as well as data loss (because the profile folder is versioned). This
  issue is regularly being reported (see e.g. the duplicates of bug
  #1616650).

  Jamie has an interesting suggestion to mitigate this situation, until
  refresh app awareness becomes default:

  « […] it would be possible for you to run something in the
  background that could occasionally see if the current symlink changed,
  and then alert to restart

  whenever refresh app awareness lands, it could be converted to see
  if something is pending, if so, prompt/alert to stop to have updates
  applied, or something

  simple idea is to nohup a script in a wrapper before invoking
  chromium proper

  iirc, firefox used to have UX built into it letting the user know
  it needed to be restarted, so there is some precedent for this sort of
  thing »

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1859878] Re: Chrome does not quit when closing the window, it remains in background

2020-04-17 Thread berkes
Not certain if this is the exact same issue, but a very similar issue
can be observed running from the commandline:

```
$ pgrep chromium | xargs kill # kill any running chromium (beware!)
$ pgrep chromium | wc -l
0 # There are non running
$ /snap/bin/chromium --product-version # command quits immediately.
$ pgrep chromium | wc -l
1
$ /snap/bin/chromium # opens a browser. 
# Quit browser manually.
$ pgrep chromium | wc -l
2
$ ps faux | grep chromium # check any processes running.
\_/bin/sh /snap/chromium/1100/bin/chromium.launcher --product-version
\_/bin/sh /snap/chromium/1100/bin/chromium.launcher
```

This shows that a process remains active after closing or running.
The `ps faux` shows the leftover running processes and clearly shows they no 
longer have a parent: it seems the parent process forks, then quits, but leaves 
its child running.

This hints at a mistake in the forking somewhere in the giant ball of
spagetti (sorry) that the snap exectuables, scripts, simlinks and
desktop files use to start a snap.

** Bug watch added: github.com/titusfortner/webdrivers/issues #168
   https://github.com/titusfortner/webdrivers/issues/168

-- 
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/1859878

Title:
  Chrome does not quit when closing the window, it remains in background

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When I close the chromium window it keeps magically running in the
  background. There is a invisible chrome icon in app indicator space
  however it can not be activated by clicking on it. The dash does not
  show that chrome is still active.  Not closing correctly further leads
  to the annoying problem chromium not saving its state when restarting.
  But this is an other problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 79.0.3945.79-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 15 22:16:17 2020
  InstallationDate: Installed on 2019-12-19 (27 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.117 
(04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019})
  Snap.ChromiumVersion:
   mkdir: cannot create directory '/run/user/0': Permission denied
   Chromium 79.0.3945.117 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-12-21 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1859878/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1859878] Re: Chrome does not quit when closing the window, it remains in background

2020-04-17 Thread berkes
Above comment comes from a bug that this behaviour introduced in a
project that uses chrome:
https://github.com/titusfortner/webdrivers/issues/168

So, besides it leaving around running processes (slightly messy) and not
closing icons (as observed by OP) it causes bugs (hanging) in scripts
and tools that wait for chrome+children to exit.

-- 
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/1859878

Title:
  Chrome does not quit when closing the window, it remains in background

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When I close the chromium window it keeps magically running in the
  background. There is a invisible chrome icon in app indicator space
  however it can not be activated by clicking on it. The dash does not
  show that chrome is still active.  Not closing correctly further leads
  to the annoying problem chromium not saving its state when restarting.
  But this is an other problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 79.0.3945.79-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 15 22:16:17 2020
  InstallationDate: Installed on 2019-12-19 (27 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.117 
(04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019})
  Snap.ChromiumVersion:
   mkdir: cannot create directory '/run/user/0': Permission denied
   Chromium 79.0.3945.117 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-12-21 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1859878/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1794655] Re: Firefox: Modal dialogs with password fields instantly hide.

2019-01-28 Thread berkes
The project name is metamask, but launchpad does not allow this to be
added. Metamask Firefox plugin is affected, so renaming to firefox for
now.

** Bug watch added: github.com/MetaMask/metamask-extension/issues #3313
   https://github.com/MetaMask/metamask-extension/issues/3313

** Also affects: gnome-shell via
   https://github.com/MetaMask/metamask-extension/issues/3313
   Importance: Unknown
   Status: Unknown

** Project changed: gnome-shell => firefox

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1794655

Title:
  Firefox: Modal dialogs with password fields instantly hide.

Status in Mozilla Firefox:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When I use Bitwarden extension by clicking on the icon, the popup
  immediately hides. See [1], although further digging suggest the bug
  was/in iBus, see [2] and [3]. Although, the source (or code path)
  originates from Gnome-Shell, see [4] and [5]. There is a propose fixed
  but it hasn't been merged. I'm reporting the issue here, so it can at
  least be tracked and I can get notified when it arrives in Ubuntu.

  Note: This issue affects all extensions that uses 'password field',
  see [6].

  
  Firefox-Version: 62.0
  Dist-Version: Ubuntu 18.04.1 LTS
  Gnome-Shell-Version: 3.28.3-0ubuntu0.18.04.2
  iBus-Version: 1.5.17-3ubuntu4

  1. https://github.com/bitwarden/browser/issues/694
  2. https://bugzilla.mozilla.org/show_bug.cgi?id=1405634#c16
  3. https://github.com/ibus/ibus/issues/2002#issuecomment-386537208
  4. https://github.com/ibus/ibus/issues/2002#issuecomment-402596959
  5. https://gitlab.gnome.org/GNOME/gnome-shell/issues/391
  6. 
https://github.com/MetaMask/metamask-extension/issues/3313#issuecomment-418677844

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1794655/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1790814] [NEW] Duplicate entries caused by debs and snaps offering the same application

2018-09-05 Thread berkes
Public bug reported:

As a user,
when I search for a software package,
I want to see either one, canonical option,
or I want to see clear visual cues why a software piece is listed multiple 
times,
So that I either don't have to choose,
Or that I have enough visual information to make a choice.

As can be seen in the screenshot, when searching for Gimp, I get two, slightly 
different options.
As a software engineer, I know the different sources: snaps and debs. And I 
know the reason for having 
two options. However, this is confusing, even when the cause is known.

We need either:

* An opinionated choice to be made: the "software" package should prefer one 
over the other. And list only that one. Commandline tools (apt, deb) still 
offer the choice to install the other option.
* A visual cue why there are two. Information lacking is: the source: "Ubuntu 
Repository (deb)" or "Snap Store". Additional information is the version: often 
one or the other is newer, or preferred. Note that after clicking the through 
to the details, this information is made avaialble, albeit small and tucked 
away at the bottom. It also does not explain much there, either.

Additionally, for sysadmins, an option to disable one or the other
entirely would be useful. This may be in place in some way already, but
I cannot find this in the configuration of the gnome-software.

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Example screenshot showing the bug."
   
https://bugs.launchpad.net/bugs/1790814/+attachment/5184829/+files/Schermafdruk%20van%202018-09-05%2010-27-22.png

-- 
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/1790814

Title:
  Duplicate entries caused by debs and snaps offering the same
  application

Status in gnome-software package in Ubuntu:
  New

Bug description:
  As a user,
  when I search for a software package,
  I want to see either one, canonical option,
  or I want to see clear visual cues why a software piece is listed multiple 
times,
  So that I either don't have to choose,
  Or that I have enough visual information to make a choice.

  As can be seen in the screenshot, when searching for Gimp, I get two, 
slightly different options.
  As a software engineer, I know the different sources: snaps and debs. And I 
know the reason for having 
  two options. However, this is confusing, even when the cause is known.

  We need either:

  * An opinionated choice to be made: the "software" package should prefer one 
over the other. And list only that one. Commandline tools (apt, deb) still 
offer the choice to install the other option.
  * A visual cue why there are two. Information lacking is: the source: "Ubuntu 
Repository (deb)" or "Snap Store". Additional information is the version: often 
one or the other is newer, or preferred. Note that after clicking the through 
to the details, this information is made avaialble, albeit small and tucked 
away at the bottom. It also does not explain much there, either.

  Additionally, for sysadmins, an option to disable one or the other
  entirely would be useful. This may be in place in some way already,
  but I cannot find this in the configuration of the gnome-software.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1790814/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1074617] Re: liferea crashes when I add a new subscription

2018-03-20 Thread berkes
Happens also when running `liferea-add-feed` which is a wrapper around
`liferea --add-feed`. The latter also causes a crash.

Attached is a strace log, created by running `strace -o liferea-
crash.log /usr/bin/liferea --add-feed
http://feeds.bbci.co.uk/news/rss.xml`.

** Attachment added: "Attached is a strace log, created by running `strace -o 
liferea-crash.log /usr/bin/liferea --add-feed 
http://feeds.bbci.co.uk/news/rss.xml`.";
   
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1074617/+attachment/5084904/+files/liferea-crash.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to liferea in Ubuntu.
https://bugs.launchpad.net/bugs/1074617

Title:
  liferea crashes when I add a new subscription

Status in liferea package in Ubuntu:
  Confirmed

Bug description:
  When I try to add a subscription using the button Liferea you close
  without completing the operation

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: liferea 1.8.3-0.1ubuntu2 [modified: usr/bin/liferea]
  Uname: Linux 3.6.5-030605-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Sat Nov  3 12:27:11 2012
  InstallationDate: Installed on 2012-09-05 (58 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  MarkForUpload: True
  SourcePackage: liferea
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1074617/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1062186] Re: 'Backup Failed' message when external backup drive first inserted

2014-10-09 Thread berkes
*** This bug is a duplicate of bug 617012 ***
https://bugs.launchpad.net/bugs/617012

I would like everyone ask who participated in this bug and is affected
by this, to mark bug #617012 as "affects me too". This way it might get
on the devlopers radar sooner.

** This bug has been marked a duplicate of bug 617012
   DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is 
already pending

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1062186

Title:
  'Backup Failed' message when external backup drive first inserted

Status in Déjà Dup Backup Tool:
  Confirmed
Status in “deja-dup” package in Ubuntu:
  Confirmed
Status in “deja-dup” package in Fedora:
  Unknown

Bug description:
  An error message entitled 'Backup Failed' with the text 'An operation
  is already pending' is displayed when I first plug in by external
  backup drive and Deja Dup attempts to perform a scheduled backup,
  although it succeeds on subsequent attempts (either scheduled or
  manual).

  The fstab entry for the drive is as follows:
  /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 
/media/thomas/Tom\040WD\040HD auto 
nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0

  I presume this is either due to both Gnome and Deja Dup attempting to
  mount the drive, or Deja Dup not waiting until the drive has been
  successfully mounted.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: deja-dup 24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  5 11:45:05 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120913)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1062186/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1062186] Re: 'Backup Failed' message when external backup drive first inserted

2013-04-26 Thread berkes
«I presume this is either due to both Gnome and Deja Dup attempting to
mount the drive, or Deja Dup not waiting until the drive has been
successfully mounted.»

Here is a trick that makes that suspicion even more probable:

1. Disconnect the drive. 
2. Log out of your account, or lock the screen.
3. Connect the drive.
4. Log-in.

On my machine, in this case, Deja-Dup wins the race and mounts the
Drive. Now Gnome complains that it cannot mount the drive becauase "it
is already in use".

Seems like a "Race-condition" mostly.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1062186

Title:
  'Backup Failed' message when external backup drive first inserted

Status in “deja-dup” package in Ubuntu:
  Confirmed

Bug description:
  An error message entitled 'Backup Failed' with the text 'An operation
  is already pending' is displayed when I first plug in by external
  backup drive and Deja Dup attempts to perform a scheduled backup,
  although it succeeds on subsequent attempts (either scheduled or
  manual).

  The fstab entry for the drive is as follows:
  /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 
/media/thomas/Tom\040WD\040HD auto 
nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0

  I presume this is either due to both Gnome and Deja Dup attempting to
  mount the drive, or Deja Dup not waiting until the drive has been
  successfully mounted.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: deja-dup 24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  5 11:45:05 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120913)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1062186/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 874260] Re: Firefox freezes when I right click or try to open up bookmarks.

2012-09-29 Thread berkes
@iiss: Why would Firefix try to open the audio-subsystem on opening the
"bookmarks" menu?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/874260

Title:
  Firefox freezes when I right click or try to open up bookmarks.

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.10
  Unity 2D
  Firefox 7.0.1
  When I right click on a link firefox freezes for a short period of time, and 
then when it un-freezes, the link I clicked on, never opens. It also freezes 
when I try to click on a bookmark on my bookmark bar, then it never opens it.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 7.0.1+build1+nobinonly-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   david  1327 F...m pulseaudio
   /dev/snd/controlC0:  david  1327 F pulseaudio
  BuildID: 20111008085056
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with AD1981B at irq 17'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x9a4'/'USB Device 0x46d:0x9a4 at usb-:00:1d.7-1, high 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:09a4'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 1 [0%] [23.00dB] [on]
  Channel: release
  Date: Fri Oct 14 10:03:17 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 24.29.24.1 dev eth0  proto static 
   24.29.24.0/23 dev eth0  proto kernel  scope link  src 24.29.25.237  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20111008085056 (Running)
  PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: 
Daemon not responding.
  PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 
1: Daemon not responding.
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago)
  dmi.bios.date: 08/01/2003
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BF86510A.15A.0043.P07.0308011434
  dmi.board.name: D865GLC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC28705-404
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: NSC45A07
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBF86510A.15A.0043.P07.0308011434:bd08/01/2003:svnGateway:pnMIDWAY:pvr4000824:rvnIntelCorporation:rnD865GLC:rvrAAC28705-404:cvnGateway:ct3:cvrNSC45A07:
  dmi.product.name: MIDWAY
  dmi.product.version: 4000824
  dmi.sys.vendor: Gateway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/874260/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 910021] Re: Cannot load Empathy Client accounts

2012-06-19 Thread berkes
I have experienced the same issue. Unfortunately the whole of empathy
hung, so I could not access "Debug menu". Only an xkill or killall would
close empathy. The error would reoccur whenever I started empathy again.

A restart of my Gnome session (logout - login) solved the issue. I now
can no longer reproduce the error.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/910021

Title:
  Cannot load Empathy Client accounts

Status in “empathy” package in Ubuntu:
  Expired

Bug description:
  Upgraded to 11.10 (from 10.04 via 10.10, 11.04). On system startup I
  get a dialogue saying:

  "There was an error while trying to connect to the Telepathy Account
  Manager. The error was:

  Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken."

  And I am unable to change my status to 'online'

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.2.0.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Fri Dec 30 08:26:47 2011
  ExecutablePath: /usr/bin/empathy
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to oneiric on 2011-12-29 (0 days ago)
  XsessionErrors:
   (empathy:2942): folks-WARNING **: Error preparing Backend 'telepathy': Did 
not receive a reply. Possible causes include: the remote application did not 
send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   (Do:2989): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
   (empathy-accounts:3736): Gtk-WARNING **: Overriding tab label for notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/910021/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 874260] Re: Firefox freezes when I right click or try to open up bookmarks.

2012-02-08 Thread berkes
Here is a screencast of how this affects me. At least in my occasion, it
seems obviously caused by many (many!) bookmarks in my menu.

Note that this is a blazingly fast machine, with lots of memory and only
SSDdrives; so the problem solves itself fast. When my bookmarks were
imported on an old/thin machine, FF halted for over 20 minutes before
becoming responsive again.

In this case, the solution clearly lies in "less bookmarks". But AFAIK
that should either be enforced by firefox not allowing more then X
bookmarks in a menu. Or firefox/unity-menu only loading a subset into
the menu.

** Attachment added: "Screencast of the freezing in action."
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/874260/+attachment/2723430/+files/out-1.ogv

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/874260

Title:
  Firefox freezes when I right click or try to open up bookmarks.

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.10
  Unity 2D
  Firefox 7.0.1
  When I right click on a link firefox freezes for a short period of time, and 
then when it un-freezes, the link I clicked on, never opens. It also freezes 
when I try to click on a bookmark on my bookmark bar, then it never opens it.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 7.0.1+build1+nobinonly-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   david  1327 F...m pulseaudio
   /dev/snd/controlC0:  david  1327 F pulseaudio
  BuildID: 20111008085056
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with AD1981B at irq 17'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x9a4'/'USB Device 0x46d:0x9a4 at usb-:00:1d.7-1, high 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:09a4'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 1 [0%] [23.00dB] [on]
  Channel: release
  Date: Fri Oct 14 10:03:17 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 24.29.24.1 dev eth0  proto static 
   24.29.24.0/23 dev eth0  proto kernel  scope link  src 24.29.25.237  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20111008085056 (Running)
  PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: 
Daemon not responding.
  PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 
1: Daemon not responding.
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago)
  dmi.bios.date: 08/01/2003
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BF86510A.15A.0043.P07.0308011434
  dmi.board.name: D865GLC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC28705-404
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: NSC45A07
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBF86510A.15A.0043.P07.0308011434:bd08/01/2003:svnGateway:pnMIDWAY:pvr4000824:rvnIntelCorporation:rnD865GLC:rvrAAC28705-404:cvnGateway:ct3:cvrNSC45A07:
  dmi.product.name: MIDWAY
  dmi.product.version: 4000824
  dmi.sys.vendor: Gateway

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/874260/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp