from:"Torsten Bronger"

[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading

2023-02-08 Thread Torsten Bronger

Of the latest crash, I attached the last 10 seconds in the log.

The URL I visited last was
https://mails.bronger.org/xx/4?tokenFull=13t4Q4g2C_ (sorry, due
to confidential content I had to replace parts of it with “x”es).  It is
a docx file.

** Attachment added: "chromium.log"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979412/+attachment/5645540/+files/chromium.log

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

Title:
  [snap] Chromium crashes when downloading

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  For a couple of weeks, I observe random crashes of Chromium when you
  click on a link that starts a non-HTML download (e.g. PDF or an MS
  Excel file).  After restarting Chromium and restoring the tabs, a
  second click on the link starts the download without problems,
  probably because this issue is not 100% reproducible in the first
  place.

  Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit)
  on Ubuntu 22.04

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


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

[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading

2023-01-29 Thread Torsten Bronger

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  [snap] Chromium crashes when downloading

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  For a couple of weeks, I observe random crashes of Chromium when you
  click on a link that starts a non-HTML download (e.g. PDF or an MS
  Excel file).  After restarting Chromium and restoring the tabs, a
  second click on the link starts the download without problems,
  probably because this issue is not 100% reproducible in the first
  place.

  Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit)
  on Ubuntu 22.04

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


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

[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading

2023-01-29 Thread Torsten Bronger

Exactly my observations. My plugins: SwitchyOmega, Dark Reader,
Idontcareaboutcookies

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

Title:
  [snap] Chromium crashes when downloading

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  For a couple of weeks, I observe random crashes of Chromium when you
  click on a link that starts a non-HTML download (e.g. PDF or an MS
  Excel file).  After restarting Chromium and restoring the tabs, a
  second click on the link starts the download without problems,
  probably because this issue is not 100% reproducible in the first
  place.

  Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit)
  on Ubuntu 22.04

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


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

[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading

2022-12-23 Thread Torsten Bronger

I wanted to collect more data first, but since Daniel has already
reported it, I must confirm that the problem is still existing.

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

Title:
  [snap] Chromium crashes when downloading

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  For a couple of weeks, I observe random crashes of Chromium when you
  click on a link that starts a non-HTML download (e.g. PDF or an MS
  Excel file).  After restarting Chromium and restoring the tabs, a
  second click on the link starts the download without problems,
  probably because this issue is not 100% reproducible in the first
  place.

  Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit)
  on Ubuntu 22.04

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


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

[Desktop-packages] [Bug 1979412] Re: [snap] Chromium crashes when downloading

2022-08-08 Thread Torsten Bronger

I don’t observe them any more.  It has never been really well
reproducible but I tend to think that the problem is gone.

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

Title:
  [snap] Chromium crashes when downloading

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  For a couple of weeks, I observe random crashes of Chromium when you
  click on a link that starts a non-HTML download (e.g. PDF or an MS
  Excel file).  After restarting Chromium and restoring the tabs, a
  second click on the link starts the download without problems,
  probably because this issue is not 100% reproducible in the first
  place.

  Observed with Chromium 102.0.5005.115 (officiel build) snap (64-Bit)
  on Ubuntu 22.04

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


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

[Desktop-packages] [Bug 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10

2022-05-12 Thread Torsten Bronger

My Chromium 101.0.4951.54 on 22.04 cannot share screen in Big Blue
Button – the shared image ist just black with the mouse pointer.

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

Title:
  Wayland Screensharing broken in Ubuntu 21.10

Status in chromium-browser package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in xdg-desktop-portal package in Ubuntu:
  Invalid
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released

Bug description:
  Freshly installed Ubuntu 21.10, screen sharing does not work with any
  browser, tested the following options:

  - Firefox snap
  - Firefox deb
  - Chromium snap
  - Chromium flatpak

  Steps to reproduce:

  1. Go to 
https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006
  2. Select to share the whole desktop in the xdg-desktop-portal
  3. Notice the orange screen share indicator in Gnome-Shell but actually 
nothing is shared in the browser.

  This should be handled high priority since this is a critical feature
  during the pandemic.

  Filed against ubuntu-meta since I don't know exactly which package to
  blame, whether it's pipewire, xdg-desktop portal or some problem
  directely with mutter / gnome-shell, please reassign accordingly.

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


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

[Desktop-packages] [Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~

2021-01-28 Thread Torsten Bronger

As lame as such comments may appear:

The level of suffering on my side is large enough to add that I too am
really irritated by this “feature”.  It is a significant obstacle in my
daily workflow, and any workaround must not be necessary in the first
place. We’ve been living with browsers with (user!) access to the whole
filesystem for decades without worrying. Besides, the software still
comes from a trusted source.

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

Title:
  [snap] chromium-browser snap cannot upload files outside ~

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  After upgrading from 19.04 to 19.10, my Chromium package was converted
  to a snap. After figuring out how to manually reconnect the password
  manager, and figuring out how to apply CHROMIUM_FLAGS that used to
  live in /etc/chromium-browser/default, and noticing that GMail is no
  longer able to play a sound when a call comes in, now I see that I am
  unable to upload files from anywhere except my home directory!
  Connecting chromium:removable-media as in
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1832711 does not help with anything else. Is there some
  way to let the file upload dialog work on any file my user account has
  access to? Or run this snap in --classic mode? If not, this seems like
  a critical limitation, as I need this multiple times a day. Switching
  to Chrome or Firefox cannot be the only workaround for this, surely?

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

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

[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it

2020-04-16 Thread Torsten Bronger

I cannot reproduce this problem anymore with Ubuntu 20.04 Beta.

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

Title:
  Full-screen window flickers once when switching to it

Status in mutter package in Ubuntu:
  New

Bug description:
  When using *some* applications (I observed it with Emacs and gnome-
  terminal) in full-screen mode, they flicker once shortly after
  switching to them with e.g. Alt-Tab.  To reproduce it:

  1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
  2. Switch to the other app with Alt-Tab.
  3. Switch back to Emacs.

  Then I observe:

  1. Emacs becomes visible.
  2. After a fraction of a second, the Emacs windows is transparent for a very 
very short time (flicker).
  3. Then, the windows is stable and usable.

  Usually, I do not observe this behaviour right from the start.  I have
  to work with the computer for a couple of minutes to see it.  I have
  been unable to find out whether a certain action triggers the problem.
  However, when it occurs, it does not go away again until the next
  restart of the X server.

  This is regression that I observe since Ubuntu 19.10.

  Changes of the graphics driver does not change anything, however, switching 
to Wayland solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-16 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1864365] Re: [snap] Dialog font missing

2020-04-02 Thread Torsten Bronger

Removing ~/snap/chromium/common/.cache/fontconfig was enough for me.  It
was not necessary to remove the whole .cache directory.

I start Chromium with a script which always removes that directory
first.  But I still observe the broken dialog boxes from time to time.

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

Title:
  [snap] Dialog font missing

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rb
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
    An open-source browser project that aims to build a safer, faster, and more 
stable way for all
    Internet users to experience the web.
  commands:
    - chromium.chromedriver
    - chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 3 days ago, at 01:56 CET
  channels:
    stable:80.0.3987.116 2020-02-19 (1036) 160MB -
    candidate: 80.0.3987.116 2020-02-19 (1036) 160MB -
    beta:  81.0.4044.17  2020-02-17 (1028) 161MB -
    edge:  81.0.4044.17  2020-02-14 (1028) 161MB -
  installed:   80.0.3987.116(1036) 160MB -

  Basic Ubuntu 19.10 installation using "factory default" font settings.

  Expected :
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, the file dialog renders normally.

  What happened instead:
  When opening any file dialog (to open or upload a file, for example) from 
Chromium snap application, all characters in the dialog box are empty squares 
(see attached screenshot).

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

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

[Desktop-packages] [Bug 1864001] Re: Dialog windows of Chromium with unprintable characters

2020-03-14 Thread Torsten Bronger

** Summary changed:

- "Save as" in chromium with unprintable characters
+ Dialog windows of Chromium with unprintable characters

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

Title:
  Dialog windows of Chromium with unprintable characters

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In Chromium with the following version numbers (output of “snap
  list”):

  chromium   80.0.3987.100   1026  stable
  canonical✓   -

  (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable
  characters, i.e., I see only small boxes instead of letters.  I don’t
  observe this in comparable dialogs of other programs, e.g. Inkscape.

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

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

[Desktop-packages] [Bug 1864001] Re: "Save as" in chromium with unprintable characters

2020-03-14 Thread Torsten Bronger

I installed Chromium directly using Snap, so apport said “Package
chromium-browser not installed and no hook available, ignoring”.

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

Title:
  "Save as" in chromium with unprintable characters

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In Chromium with the following version numbers (output of “snap
  list”):

  chromium   80.0.3987.100   1026  stable
  canonical✓   -

  (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable
  characters, i.e., I see only small boxes instead of letters.  I don’t
  observe this in comparable dialogs of other programs, e.g. Inkscape.

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

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

[Desktop-packages] [Bug 1864001] Re: "Save as" in chromium with unprintable characters

2020-03-14 Thread Torsten Bronger

I attached a screenshot showing the problem.

** Attachment added: "The “open file“ dialog as opened with Ctrl+o."
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864001/+attachment/5337011/+files/Bildschirmfoto%20von%202020-03-14%2022-33-50.png

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => 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/1864001

Title:
  "Save as" in chromium with unprintable characters

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In Chromium with the following version numbers (output of “snap
  list”):

  chromium   80.0.3987.100   1026  stable
  canonical✓   -

  (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable
  characters, i.e., I see only small boxes instead of letters.  I don’t
  observe this in comparable dialogs of other programs, e.g. Inkscape.

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

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

[Desktop-packages] [Bug 1864001] Re: "Save as" in chromium with unprintable characters

2020-03-14 Thread Torsten Bronger

I found out that a workaround is to remove
~/snap/chromium/common/.cache/fontconfig before starting Chromium.

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

Title:
  "Save as" in chromium with unprintable characters

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In Chromium with the following version numbers (output of “snap
  list”):

  chromium   80.0.3987.100   1026  stable
  canonical✓   -

  (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable
  characters, i.e., I see only small boxes instead of letters.  I don’t
  observe this in comparable dialogs of other programs, e.g. Inkscape.

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

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

[Desktop-packages] [Bug 1864001] [NEW] "Save as" in chromium with unprintable characters

2020-02-19 Thread Torsten Bronger

Public bug reported:

In Chromium with the following version numbers (output of “snap list”):

chromium   80.0.3987.100   1026  stable
canonical✓   -

(Ubuntu 19.10) the “Save as” dialog box consists only of unprintable
characters, i.e., I see only small boxes instead of letters.  I don’t
observe this in comparable dialogs of other programs, e.g. Inkscape.

** Affects: chromium-browser (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/1864001

Title:
  "Save as" in chromium with unprintable characters

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In Chromium with the following version numbers (output of “snap
  list”):

  chromium   80.0.3987.100   1026  stable
  canonical✓   -

  (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable
  characters, i.e., I see only small boxes instead of letters.  I don’t
  observe this in comparable dialogs of other programs, e.g. Inkscape.

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

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

[Desktop-packages] [Bug 1864001] Re: "Save as" in chromium with unprintable characters

2020-02-19 Thread Torsten Bronger

I just updated Chromium to

chromium   80.0.3987.116   1036  stable
canonical✓   -

and still observe this bug.

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

Title:
  "Save as" in chromium with unprintable characters

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In Chromium with the following version numbers (output of “snap
  list”):

  chromium   80.0.3987.100   1026  stable
  canonical✓   -

  (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable
  characters, i.e., I see only small boxes instead of letters.  I don’t
  observe this in comparable dialogs of other programs, e.g. Inkscape.

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

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

[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it

2020-01-31 Thread Torsten Bronger

** Attachment added: "dpkgs.txt"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324387/+files/dpkgs.txt

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

Title:
Full-screen window flickers once when switching to it

Status in gnome-shell package in Ubuntu:
Incomplete

Bug description:
When using *some* applications (I observed it with Emacs and gnome-
terminal) in full-screen mode, they flicker once shortly after
switching to them with e.g. Alt-Tab. To reproduce it:

1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
2. Switch to the other app with Alt-Tab.
3. Switch back to Emacs.

Then I observe:

1. Emacs becomes visible.
2. After a fraction of a second, the Emacs windows is transparent for a very
very short time (flicker).
3. Then, the windows is stable and usable.

Usually, I do not observe this behaviour right from the start. I have
to work with the computer for a couple of minutes to see it. I have
been unable to find out whether a certain action triggers the problem.
However, when it occurs, it does not go away again until the next
restart of the X server.

This is regression that I observe since Ubuntu 19.10.

Changes of the graphics driver does not change anything, however, switching
to Wayland solves the problem.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-11-16 (75 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Tags: eoan
Uname: Linux 5.3.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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

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

[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it

2020-01-31 Thread Torsten Bronger

** Attachment added: "journal.txt"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324388/+files/journal.txt

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

Title:
Full-screen window flickers once when switching to it

Status in gnome-shell package in Ubuntu:
Incomplete

1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
2. Switch to the other app with Alt-Tab.
3. Switch back to Emacs.

Then I observe:

1. Emacs becomes visible.
2. After a fraction of a second, the Emacs windows is transparent for a very
very short time (flicker).
3. Then, the windows is stable and usable.

This is regression that I observe since Ubuntu 19.10.

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

[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it

2020-01-31 Thread Torsten Bronger

** Attachment added: "lspcik.txt"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324389/+files/lspcik.txt

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

Title:
Full-screen window flickers once when switching to it

Status in gnome-shell package in Ubuntu:
Incomplete

1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
2. Switch to the other app with Alt-Tab.
3. Switch back to Emacs.

Then I observe:

1. Emacs becomes visible.
2. After a fraction of a second, the Emacs windows is transparent for a very
very short time (flicker).
3. Then, the windows is stable and usable.

This is regression that I observe since Ubuntu 19.10.

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

[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it

2020-01-31 Thread Torsten Bronger

** Attachment added: "dmesg.txt"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324386/+files/dmesg.txt

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

Title:
Full-screen window flickers once when switching to it

Status in gnome-shell package in Ubuntu:
Incomplete

1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
2. Switch to the other app with Alt-Tab.
3. Switch back to Emacs.

Then I observe:

1. Emacs becomes visible.
2. After a fraction of a second, the Emacs windows is transparent for a very
very short time (flicker).
3. Then, the windows is stable and usable.

This is regression that I observe since Ubuntu 19.10.

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

[Desktop-packages] [Bug 1861391] ProcCpuinfoMinimal.txt

2020-01-30 Thread Torsten Bronger

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1861391/+attachment/5324376/+files/ProcCpuinfoMinimal.txt

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

Title:
  Full-screen window flickers once when switching to it

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using *some* applications (I observed it with Emacs and gnome-
  terminal) in full-screen mode, they flicker once shortly after
  switching to them with e.g. Alt-Tab.  To reproduce it:

  1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
  2. Switch to the other app with Alt-Tab.
  3. Switch back to Emacs.

  Then I observe:

  1. Emacs becomes visible.
  2. After a fraction of a second, the Emacs windows is transparent for a very 
very short time (flicker).
  3. Then, the windows is stable and usable.

  Usually, I do not observe this behaviour right from the start.  I have
  to work with the computer for a couple of minutes to see it.  I have
  been unable to find out whether a certain action triggers the problem.
  However, when it occurs, it does not go away again until the next
  restart of the X server.

  This is regression that I observe since Ubuntu 19.10.

  Changes of the graphics driver does not change anything, however, switching 
to Wayland solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-16 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1861391] ProcEnviron.txt

2020-01-30 Thread Torsten Bronger

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1861391/+attachment/5324377/+files/ProcEnviron.txt

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

Title:
  Full-screen window flickers once when switching to it

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using *some* applications (I observed it with Emacs and gnome-
  terminal) in full-screen mode, they flicker once shortly after
  switching to them with e.g. Alt-Tab.  To reproduce it:

  1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
  2. Switch to the other app with Alt-Tab.
  3. Switch back to Emacs.

  Then I observe:

  1. Emacs becomes visible.
  2. After a fraction of a second, the Emacs windows is transparent for a very 
very short time (flicker).
  3. Then, the windows is stable and usable.

  Usually, I do not observe this behaviour right from the start.  I have
  to work with the computer for a couple of minutes to see it.  I have
  been unable to find out whether a certain action triggers the problem.
  However, when it occurs, it does not go away again until the next
  restart of the X server.

  This is regression that I observe since Ubuntu 19.10.

  Changes of the graphics driver does not change anything, however, switching 
to Wayland solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-16 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it

2020-01-30 Thread Torsten Bronger

apport information

** Tags added: apport-collected eoan

** Description changed:

  When using *some* applications (I observed it with Emacs and gnome-
  terminal) in full-screen mode, they flicker once shortly after switching
  to them with e.g. Alt-Tab.  To reproduce it:
  
  1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
  2. Switch to the other app with Alt-Tab.
  3. Switch back to Emacs.
  
  Then I observe:
  
  1. Emacs becomes visible.
  2. After a fraction of a second, the Emacs windows is transparent for a very 
very short time (flicker).
  3. Then, the windows is stable and usable.
  
  Usually, I do not observe this behaviour right from the start.  I have
  to work with the computer for a couple of minutes to see it.  I have
  been unable to find out whether a certain action triggers the problem.
  However, when it occurs, it does not go away again until the next
  restart of the X server.
  
  This is regression that I observe since Ubuntu 19.10.
  
- Changes of the graphics driver does not change anything, however,
- switching to Wayland solves the problem.
+ Changes of the graphics driver does not change anything, however, switching 
to Wayland solves the problem.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-11-16 (75 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
+ Tags:  eoan
+ Uname: Linux 5.3.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1861391/+attachment/5324375/+files/Dependencies.txt

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

Title:
  Full-screen window flickers once when switching to it

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using *some* applications (I observed it with Emacs and gnome-
  terminal) in full-screen mode, they flicker once shortly after
  switching to them with e.g. Alt-Tab.  To reproduce it:

  1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
  2. Switch to the other app with Alt-Tab.
  3. Switch back to Emacs.

  Then I observe:

  1. Emacs becomes visible.
  2. After a fraction of a second, the Emacs windows is transparent for a very 
very short time (flicker).
  3. Then, the windows is stable and usable.

  Usually, I do not observe this behaviour right from the start.  I have
  to work with the computer for a couple of minutes to see it.  I have
  been unable to find out whether a certain action triggers the problem.
  However, when it occurs, it does not go away again until the next
  restart of the X server.

  This is regression that I observe since Ubuntu 19.10.

  Changes of the graphics driver does not change anything, however, switching 
to Wayland solves the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-16 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1861391] Re: Full-screen window flickers once when switching to it

2020-01-30 Thread Torsten Bronger

I am not sure whether it is really the gnome-shell that it responsible.
However, it happens with more than one application (Emacs and the
terminal window), and I can exclude the graphics driver.

** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  Full-screen window flickers once when switching to it

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When using *some* applications (I observed it with Emacs and gnome-
  terminal) in full-screen mode, they flicker once shortly after
  switching to them with e.g. Alt-Tab.  To reproduce it:

  1. Open Emacs in full-screen mode and one other application (e.g. Chromium).
  2. Switch to the other app with Alt-Tab.
  3. Switch back to Emacs.

  Then I observe:

  1. Emacs becomes visible.
  2. After a fraction of a second, the Emacs windows is transparent for a very 
very short time (flicker).
  3. Then, the windows is stable and usable.

  Usually, I do not observe this behaviour right from the start.  I have
  to work with the computer for a couple of minutes to see it.  I have
  been unable to find out whether a certain action triggers the problem.
  However, when it occurs, it does not go away again until the next
  restart of the X server.

  This is regression that I observe since Ubuntu 19.10.

  Changes of the graphics driver does not change anything, however,
  switching to Wayland solves the problem.

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

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

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-16 Thread Torsten Bronger

I reported it at .

** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues #40
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/40

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

Title:
NetworkManager ignores pushed openvpn routes

Status in network-manager-openvpn package in Ubuntu:
Confirmed

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

1) Use an OpenVpn server that pushes routes. I suggest using a server
that pushes several routes since this makes their absence obvious.
Set up a NetworkManager VPN of type OpenVpn to this server. Select
"Use this connection only for resources on its network" in the
"Routes" section of the IPV4 options.

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

The missing routes are also "Resources on the VPN network", and should be
added in the absence of further direction. Ignoring pushed routes should be
controlled by the "Ignore automatically obtained routes" checkbox.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-openvpn 1.1.93-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Fri Jul 15 23:12:55 2016
InstallationDate: Installed on 2016-05-04 (72 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+subscriptions

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-15 Thread Torsten Bronger

[Re-posted because I accidentally clicked on “Post Comment”. Sorry for
that.]

Confirmed with Ubuntu 19.04. An

push "route 134.94.0.0 255.255.0.0 net_gateway"

is ignored. The pushed route is mentioned in the NetworkManager log:

NetworkManager[893]: […] Data: Static Route: 134.94.0.0/16
Next Hop: 134.94.16.1

(The gateway is even correct.) However, no route is actually added.
Interestingly enough, a

push "route 134.94.0.0 255.255.0.0 vpn_gateway"

*is* added to the routes. I suspect the device is wrong, because a
manual

# route add -net 134.94.0.0/16 gw 134.94.16.1 dev tun0
SIOCADDRT: Network is unreachable

fails obviously. Instead of “tun0”, it must be the normal net device
for which the gateway is valid. Possibly, NetworkManager tries to add
the route to “tun0” always, which would be wrong.

Is there an upstream bug report?

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

Title:
NetworkManager ignores pushed openvpn routes

Status in network-manager-openvpn package in Ubuntu:
Confirmed

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+subscriptions

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-15 Thread Torsten Bronger

Confirmed with Ubuntu 19.04. An

push "route 134.94.0.0 255.255.0.0 net_gateway"

is ignored. The pushed route is mentioned in the NetworkManager log:

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

Title:
NetworkManager ignores pushed openvpn routes

Status in network-manager-openvpn package in Ubuntu:
Confirmed

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+subscriptions

[Desktop-packages] [Bug 1385009] Re: Hangs up on text edit

2016-12-15 Thread Torsten Bronger

GTK_IM_MODULE is "xim" on my system.  I don't know where this default
comes from, though.

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

Title:
  Hangs up on text edit

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Incomplete

Bug description:
  Inkscape window became not responding when I edited an simple text
  element in simple svg.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: inkscape 0.48.5-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 11:24:51 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2014-09-17 (36 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140916)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1385009] Re: Hangs up on text edit

2016-12-14 Thread Torsten Bronger

This still is a problem on Lubuntu 16.10, and "unset GTK_IM_MODULE" is
still a workaround.

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

Title:
  Hangs up on text edit

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Incomplete

Bug description:
  Inkscape window became not responding when I edited an simple text
  element in simple svg.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: inkscape 0.48.5-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 11:24:51 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2014-09-17 (36 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140916)
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1647706] [NEW] Totem crashes with segmentation fault and Clutter error

2016-12-06 Thread Torsten Bronger

Public bug reported:

On Ubuntu 16.10, Totem crashes immediately after startup with the
following error:

** (totem:29792): WARNING **: Error retrieving accessibility bus
address: org.freedesktop.DBus.Error.ServiceUnknown: The name
org.a11y.Bus was not provided by any .service files

(totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter: Unable
to initialize the Clutter backend

(totem:29792): Totem-WARNING **: gtk-clutter failed to initialise,
expect problems from here on.

(totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter: Unable
to initialize the Clutter backend

(totem:29792): Clutter-WARNING **: Missing Cogl context: was Clutter correctly 
initialized?
Segmentation fault (core dumped)


I use the package “nvidia-304” as my video driver.

** Affects: totem (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Totem crashes with segmentation fault and Clutter error

Status in totem package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.10, Totem crashes immediately after startup with the
  following error:

  ** (totem:29792): WARNING **: Error retrieving accessibility bus
  address: org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.a11y.Bus was not provided by any .service files

  (totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter:
  Unable to initialize the Clutter backend

  (totem:29792): Totem-WARNING **: gtk-clutter failed to initialise,
  expect problems from here on.

  (totem:29792): Clutter-CRITICAL **: Unable to initialize Clutter:
  Unable to initialize the Clutter backend

  (totem:29792): Clutter-WARNING **: Missing Cogl context: was Clutter 
correctly initialized?
  Segmentation fault (core dumped)

  
  I use the package “nvidia-304” as my video driver.

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

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

[Desktop-packages] [Bug 1563219] [NEW] Cannot leave fullscreen mode

2016-03-29 Thread Torsten Bronger

Public bug reported:

When using Chromium in fullscreen mode and pressing F11, the menu canvas
(tabs, URL line, bookmarks etc) are not restored.  Instead, you only see
the HTML page, rendering chromium unusable.  One has to restart it.

This is partly a regression, because until one week ago, there was a
workaround by moving the mouse to the window top and clicking on
"leaving fullscreen mode".  This feature was switched off in a recent
update, so you have to press F11 -- which does not work.

** Affects: chromium-browser (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/1563219

Title:
  Cannot leave fullscreen mode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When using Chromium in fullscreen mode and pressing F11, the menu
  canvas (tabs, URL line, bookmarks etc) are not restored.  Instead, you
  only see the HTML page, rendering chromium unusable.  One has to
  restart it.

  This is partly a regression, because until one week ago, there was a
  workaround by moving the mouse to the window top and clicking on
  "leaving fullscreen mode".  This feature was switched off in a recent
  update, so you have to press F11 -- which does not work.

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

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

[Desktop-packages] [Bug 1563219] Re: Cannot leave fullscreen mode

2016-03-29 Thread Torsten Bronger

I tested Chromium on Lubuntu 14.04 and Lubuntu 15.10.

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

Title:
  Cannot leave fullscreen mode

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When using Chromium in fullscreen mode and pressing F11, the menu
  canvas (tabs, URL line, bookmarks etc) are not restored.  Instead, you
  only see the HTML page, rendering chromium unusable.  One has to
  restart it.

  This is partly a regression, because until one week ago, there was a
  workaround by moving the mouse to the window top and clicking on
  "leaving fullscreen mode".  This feature was switched off in a recent
  update, so you have to press F11 -- which does not work.

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

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

[Desktop-packages] [Bug 1284635] Re: IBus does not support certain keyboard layouts

2014-11-16 Thread Torsten Bronger

For the time being, does anybody have a workaround for deactivating dead
keys in spite of this bug?  It would be very helpful for programmers
like me.

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

Title:
  IBus does not support certain keyboard layouts

Status in “ibus” package in Ubuntu:
  Triaged
Status in “ibus” source package in Trusty:
  Triaged

Bug description:
  installed trusty beta1 with keyboard layout set correctly during
  install

  install completes, login to new install - layout as set during install

  once logged in - layout set to US and keyboard layout set during
  install is missing from list

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Feb 25 12:55:56 2014
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1265558] Re: Crippled glyphs in X

2014-08-14 Thread Torsten Bronger

I cannot reproduce it anymore in Lubuntu 14.04.

** Changed in: xorg (Ubuntu)
   Status: New = Fix Released

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

Title:
  Crippled glyphs in X

Status in “xorg” package in Ubuntu:
  Fix Released

Bug description:
  Every now and then, I see single crippled glyphs in my windows.  So
  far, it occured on the bash console window, Emacs, and Chromium, so I
  can safely say that it must have something to do with the X system
  itself or the window manager.  I attached a screenshot exhibiting this
  problem.

  It happens after opening a window or scrolling.  Marking the
  characters with the mouse or otherwise forcing a redraw restores the
  glyph.

  It occurs since Ubuntu 13.10.  Before that, I've never seen something like 
this.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2011-11-15 (831 days ago)
  InstallationMedia: Lubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  Package: xorg 1:7.7+1ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2014-01-02 (52 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1355028] [NEW] No no dead keys option anymore

2014-08-11 Thread Torsten Bronger

Public bug reported:

I use Lubuntu 14.04.  Since this version, I cannot switch off dead keys,
i.e. I have to press the acute accent key twice to see the character.  I
cannot select a no dead key version of German keyboard layout in the
ibus tray icon menue.

This is although I could select German -- no dead keys during the
installation of Lubuntu.

** Affects: ibus (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No no dead keys option anymore

Status in “ibus” package in Ubuntu:
  New

Bug description:
  I use Lubuntu 14.04.  Since this version, I cannot switch off dead
  keys, i.e. I have to press the acute accent key twice to see the
  character.  I cannot select a no dead key version of German keyboard
  layout in the ibus tray icon menue.

  This is although I could select German -- no dead keys during the
  installation of Lubuntu.

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

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

[Desktop-packages] [Bug 1307648] Re: chromium 34 from proposed does not take input from keyboard in first entry point on several webpages

2014-08-10 Thread Torsten Bronger

The problem has gone on my system with one of the official updates of
this week.

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

Title:
  chromium 34 from proposed does not take input from keyboard in first
  entry point on several webpages

Status in “chromium-browser” package in Ubuntu:
  Confirmed

Bug description:
  To reproduce install chromium 34 from proposed with pepperflash. And
  find a site that you input some text into like indeed.com or some
  others. Then you hit the keys on the keyboard but no text is seen
  onscreen.

  I expected the text to be entering into chroumium like it is on any
  other browser. And for the text to be entered into the browser and
  transfered ot the webpage I am submitting it to.

  Instead it did not show up and indeed.com thought I did not enter anything 
even though I pressed several keys on my keyboard. 
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  chromium-browser:
Installed: 34.0.1847.116-0ubuntu1~pkg1006
Candidate: 34.0.1847.116-0ubuntu1~pkg1006
Version table:
   *** 34.0.1847.116-0ubuntu1~pkg1006 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   33.0.1750.152-0ubuntu1~pkg995.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu1~pkg1006
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 14 11:15:07 2014
  Desktop-Session:
   DESKTOP_SESSION = Lubuntu
   XDG_CONFIG_DIRS = 
/etc/xdg/lubuntu:/etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/etc/xdg/lubuntu:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/share/Lubuntu:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sdc4  
ext4  641G   61G  549G  10% /\nnone   tmpfs 4.0K 0  4.0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1.9G  4.0K  1.9G   1% /dev\ntmpfs   
   tmpfs 386M  1.3M  385M   1% /run\nnone   tmpfs 5.0M 
0  5.0M   0% /run/lock\nnone   tmpfs 1.9G   17M  1.9G   1% 
/run/shm\nnone   tmpfs 100M   16K  100M   1% /run/user\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sdc4 41M  
565K   41M2% /\nnone 483K 2  483K1% 
/sys/fs/cgroup\nudev 480K   612  479K1% /dev\ntmpfs
483K   643  482K1% /run\nnone 483K 5  483K1% 
/run/lock\nnone 483K19  483K1% /run/shm\nnone 
483K13  483K1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-01-02 (102 days ago)
  InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64 (20140101)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-14T10:56:12.681598

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

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

[Desktop-packages] [Bug 1284635] Re: IBus does not support certain keyboard layouts

2014-07-28 Thread Torsten Bronger

I'd like to add that, apart from the fact that keyboard inputs in
Chromium don't work, I cannot have a no dead keys configuration due to
this bug, i.e. I have to hit the accent keys twice to see the character.

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

Title:
  IBus does not support certain keyboard layouts

Status in “ibus” package in Ubuntu:
  Triaged
Status in “ibus” source package in Trusty:
  Triaged

Bug description:
  installed trusty beta1 with keyboard layout set correctly during
  install

  install completes, login to new install - layout as set during install

  once logged in - layout set to US and keyboard layout set during
  install is missing from list

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Feb 25 12:55:56 2014
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1284635] Re: IBus does not support certain keyboard layouts

2014-05-11 Thread Torsten Bronger

I currently apply the workaround to right-click on this keyboard icon in
the panel and click on quit.  I think this is the purging ibus
thing, right?

Anyway, my --for me-- important question is: Is this purging of ibus
responsible for xfce freezing every other day?  It doesn't happen
frequently but it means that I lose all running applications and have to
restart lxsession.

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

Title:
  IBus does not support certain keyboard layouts

Status in “ibus” package in Ubuntu:
  Triaged
Status in “ibus” source package in Trusty:
  Triaged

Bug description:
  installed trusty beta1 with keyboard layout set correctly during
  install

  install completes, login to new install - layout as set during install

  once logged in - layout set to US and keyboard layout set during
  install is missing from list

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Feb 25 12:55:56 2014
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1313047] [NEW] Mouse-selecting URL doesn't include protocol prefix

2014-04-26 Thread Torsten Bronger

Public bug reported:

In Lubuntu 14.04, when selecting the URL in Chromium with the mouse and
pasting it by middle-clicking, the pretocol prefix http://; is not
included into the result.  (If you copy it to the clipboard with Ctrl+C,
it is, however.)

This is a regression from Lubuntu 13.10, up to which this has worked
nicely.

** Affects: chromium-browser (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/1313047

Title:
  Mouse-selecting URL doesn't include protocol prefix

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  In Lubuntu 14.04, when selecting the URL in Chromium with the mouse
  and pasting it by middle-clicking, the pretocol prefix http://; is
  not included into the result.  (If you copy it to the clipboard with
  Ctrl+C, it is, however.)

  This is a regression from Lubuntu 13.10, up to which this has worked
  nicely.

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

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

[Desktop-packages] [Bug 1265558] Re: Crippled glyphs in X

2014-02-23 Thread Torsten Bronger

apport information

** Tags added: apport-collected saucy

** Description changed:

  Every now and then, I see single crippled glyphs in my windows.  So far,
  it occured on the bash console window, Emacs, and Chromium, so I can
  safely say that it must have something to do with the X system itself or
  the window manager.  I attached a screenshot exhibiting this problem.
  
  It happens after opening a window or scrolling.  Marking the characters
  with the mouse or otherwise forcing a redraw restores the glyph.
  
- It occurs since Ubuntu 13.10.  Before that, I've never seen something
- like this.
+ It occurs since Ubuntu 13.10.  Before that, I've never seen something like 
this.
+ --- 
+ ApportVersion: 2.12.5-0ubuntu2.2
+ Architecture: amd64
+ DistroRelease: Ubuntu 13.10
+ InstallationDate: Installed on 2011-11-15 (831 days ago)
+ InstallationMedia: Lubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
+ MarkForUpload: True
+ Package: xorg 1:7.7+1ubuntu6
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
+ Tags:  saucy
+ Uname: Linux 3.11.0-15-generic x86_64
+ UpgradeStatus: Upgraded to saucy on 2014-01-02 (52 days ago)
+ UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1265558/+attachment/3993697/+files/Dependencies.txt

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

Title:
  Crippled glyphs in X

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Every now and then, I see single crippled glyphs in my windows.  So
  far, it occured on the bash console window, Emacs, and Chromium, so I
  can safely say that it must have something to do with the X system
  itself or the window manager.  I attached a screenshot exhibiting this
  problem.

  It happens after opening a window or scrolling.  Marking the
  characters with the mouse or otherwise forcing a redraw restores the
  glyph.

  It occurs since Ubuntu 13.10.  Before that, I've never seen something like 
this.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2011-11-15 (831 days ago)
  InstallationMedia: Lubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  Package: xorg 1:7.7+1ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2014-01-02 (52 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1265558] ProcEnviron.txt

2014-02-23 Thread Torsten Bronger

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1265558/+attachment/3993698/+files/ProcEnviron.txt

** Changed in: xorg (Ubuntu)
   Status: Incomplete = 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/1265558

Title:
  Crippled glyphs in X

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Every now and then, I see single crippled glyphs in my windows.  So
  far, it occured on the bash console window, Emacs, and Chromium, so I
  can safely say that it must have something to do with the X system
  itself or the window manager.  I attached a screenshot exhibiting this
  problem.

  It happens after opening a window or scrolling.  Marking the
  characters with the mouse or otherwise forcing a redraw restores the
  glyph.

  It occurs since Ubuntu 13.10.  Before that, I've never seen something like 
this.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2011-11-15 (831 days ago)
  InstallationMedia: Lubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  Package: xorg 1:7.7+1ubuntu6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Tags:  saucy
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2014-01-02 (52 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1036830] Re: Can't log in unless remove .Xauthority or use gdm

2013-09-23 Thread Torsten Bronger

I suffer from this bug for a week now.  I have no idea what causes this.
I use Lubuntu 13.04.  My hobe directory is mounted with NFS, but for
years, so this cannot be the sole cause.

My workaround is to remove /home/bronger/.Xauthority through
/etc/rc.local.

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

Title:
  Can't log in unless remove .Xauthority or use gdm

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  On 8/13/2012 I updated ubuntu 12.10.  Now when I try to log in the
  system flashes a black screen and then puts me back at the log in
  screen.  Logging in as guest works.  I tried adding a new user and
  cannot log in with that user either.

  I switched to gdm and logging in works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
  Uname: Linux 3.5.0-10-generic x86_64
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  Date: Tue Aug 14 13:24:06 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04a9]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: Dell Inc. Latitude E6220
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-10-generic 
root=UUID=94ff83ca-e880-49d3-8791-cdd2999ea806 ro quiet splash 
elevator=deadline vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   section Device
Identifier  Card0
Driver  intel
Option  AccelMethod sna
   EndSection
  dmi.bios.date: 05/17/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0D1CTR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd05/17/2012:svnDellInc.:pnLatitudeE6220:pvr01:rvnDellInc.:rn0D1CTR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6220
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.38-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~really6.14.4-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1

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

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

[Desktop-packages] [Bug 1122833] Re: Raw color setting produces semi-transparent TIFF with -h

2013-08-02 Thread Torsten Bronger

Since dcraw v9.18, this bug is fixed upstream.

Still no feedback from Dave Coffin though, and no release notes either.
:-(

** Changed in: dcraw (Ubuntu)
   Status: New = Fix Committed

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

Title:
  Raw color setting produces semi-transparent TIFF with -h

Status in “dcraw” package in Ubuntu:
  Fix Committed

Bug description:
  dcraw -T -h -o 0 DSC06156.ARW

  produces a semi-transparent TIFF.  What I expect is a non-transparent
  TIFF with the quarter area of

  dcraw -T -o 0 DSC06156.ARW

  I observe this bug in v9.16 and v9.17.  In particular, v8.99 is not
  affected, but it doesn't support my camera really.

  See the example:
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.ARW
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.tiff

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

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

[Desktop-packages] [Bug 1122833] Re: Raw color setting produces semi-transparent TIFF with -h

2013-03-10 Thread Torsten Bronger

Yes, I wrote an email describing the problem to dcof...@cybercom.net 8
weeks ago.  However, there hasn't been any reply.

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

Title:
  Raw color setting produces semi-transparent TIFF with -h

Status in “dcraw” package in Ubuntu:
  New

Bug description:
  dcraw -T -h -o 0 DSC06156.ARW

  produces a semi-transparent TIFF.  What I expect is a non-transparent
  TIFF with the quarter area of

  dcraw -T -o 0 DSC06156.ARW

  I observe this bug in v9.16 and v9.17.  In particular, v8.99 is not
  affected, but it doesn't support my camera really.

  See the example:
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.ARW
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.tiff

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

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

[Desktop-packages] [Bug 777882] Re: xmodmap not honored

2013-02-26 Thread Torsten Bronger

I confirm this on Lubuntu 12.10.  An .Xmodmap file with

remove lock = Caps_Lock

has no effect, however,

keycode 66 =

successfully switches off Caps Lock (where the keycode is correct).

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

Title:
  xmodmap not honored

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xorg

  In maverick, I disabled caps lock by having the line 'clear Lock' in 
~/.Xmodmap
  Upon upgrade to natty, .Xmodmap is still being read, and the output of 
xmodmap reflects it:

  $ xmodmap
  shift   Shift_L (0x32),  Shift_R (0x3e)
  lock  
  control Control_L (0x25),  Caps_Lock (0x42),  Control_R (0x69)
  mod1Alt_L (0x40),  Alt_R (0x6c),  Meta_L (0xcd)
  mod2Num_Lock (0x4d)
  mod3  
  mod4Super_L (0x85),  Super_R (0x86),  Super_L (0xce),  Hyper_L (0xcf)
  mod5ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)

  But the xmodmap state is not honored and caps lock is still caps lock.
  Rerunning xmodmap ~/.Xmodmap changes nothing.

  See also: http://ubuntuforums.org/showthread.php?t=1743145

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: xserver-xorg 1:7.6+4ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: openafs
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1024x600
   edid-base64: 
AP///wAw5AYCAAATAQOAFg14CtOFlVlWjiggUFQBAQEBAQEBAQEBAQEBAQEBBhgAuEFYZCAwIDYA4H4b/gBGMDUwVIExMDFXU0EKAAEBCiAgABU=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  Date: Thu May  5 10:15:18 2011
  DistUpgraded: Log time: 2011-05-01 23:16:23.271461
  DistroCodename: natty
  DistroVariant: ubuntu
  DkmsStatus:
   openafs, 1.4.14, 2.6.35-28-generic, i686: installed 
   openafs, 1.4.14, 2.6.38-8-generic, i686: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:041a]
 Subsystem: Dell Device [1028:041a]
  InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 
(20101007)
  MachineType: Dell Inc. Inspiron 1012
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=4d929c20-c796-4eab-96b6-8612ab308e23 ro quiet splash vt.handoff=7
  Renderer: Unknown
  SourcePackage: xorg
  UpgradeStatus: Upgraded to natty on 2011-05-02 (2 days ago)
  dmi.bios.date: 02/22/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0P9MDV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd02/22/2010:svnDellInc.:pnInspiron1012:pvrA06:rvnDellInc.:rn0P9MDV:rvrA06:cvnDellInc.:ct8:cvrA06:
  dmi.product.name: Inspiron 1012
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
  version.libdrm2: libdrm2 2.4.23-1ubuntu6
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
  version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/777882/+subscriptions

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

[Desktop-packages] [Bug 1074755] Re: Chromium not maximized after fullscreen

2013-02-17 Thread Torsten Bronger

*** This bug is a duplicate of bug 931282 ***
https://bugs.launchpad.net/bugs/931282

** This bug has been marked a duplicate of bug 931282
   Leaving fullscreen of chromium doesn't restore maximized window

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

Title:
  Chromium not maximized after fullscreen

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Reproduced on Lubuntu 12.04 and Lubuntu 12.10.

  Steps to reproduce:

  1. Maximize Chromium e.g. with the second buttom in the top right corder of 
the window frame.
  1. Switch Chromium to fullscreen with F11.
  2. Switch back by pressing F11 again.

  What I see:

  Chromium's window is not maximized anymore.

  What I expect:

  The same status as after step (1), e.g. a maximised window.

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

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

[Desktop-packages] [Bug 1124334] Re: Chromium cannot open profile correctly after system crash

2013-02-17 Thread Torsten Bronger

Related upstream bug report is
http://code.google.com/p/chromium/issues/detail?id=27756

** Bug watch added: code.google.com/p/chromium/issues #27756
   http://code.google.com/p/chromium/issues/detail?id=27756

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

Title:
  Chromium cannot open profile correctly after system crash

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  After a system crash, Chromium opens two dialog boxes showing

  You profile could not be opened correctly

  It doesn't offer any further explanations, and doesn't try to fix it
  by itself.  I found out that I have to remove
  ~/.config/chromium/Default/{Web Data,History}.  Then, I can use
  Chromium normally.  However, the data in those files is lost.

  Instead, Chromium should write to those files in a way that the data
  cannot be get corrupted in a crash.  Until this is realised, Chromium
  should at least offer to remove the corrupted files by itself.

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

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

[Desktop-packages] [Bug 1124334] [NEW] Chromium cannot open profile correctly after system crash

2013-02-13 Thread Torsten Bronger

Public bug reported:

After a system crash, Chromium opens two dialog boxes showing

You profile could not be opened correctly

It doesn't offer any further explanations, and doesn't try to fix it by
itself.  I found out that I have to remove
~/.config/chromium/Default/{Web Data,History}.  Then, I can use
Chromium normally.  However, the data in those files is lost.

Instead, Chromium should write to those files in a way that the data
cannot be get corrupted in a crash.  Until this is realised, Chromium
should at least offer to remove the corrupted files by itself.

** Affects: chromium-browser (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/1124334

Title:
  Chromium cannot open profile correctly after system crash

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  After a system crash, Chromium opens two dialog boxes showing

  You profile could not be opened correctly

  It doesn't offer any further explanations, and doesn't try to fix it
  by itself.  I found out that I have to remove
  ~/.config/chromium/Default/{Web Data,History}.  Then, I can use
  Chromium normally.  However, the data in those files is lost.

  Instead, Chromium should write to those files in a way that the data
  cannot be get corrupted in a crash.  Until this is realised, Chromium
  should at least offer to remove the corrupted files by itself.

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

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

[Desktop-packages] [Bug 1122833] [NEW] Raw color output fails with -h

2013-02-12 Thread Torsten Bronger

Public bug reported:

draw -T -h -o 0 DSC1.ARW

produces a semi-transparent TIFF.  What I expect is a non-transparent
TIFF with the quarter area of

draw -T -o 0 DSC1.ARW

I observe this bug in v9.16 and v9.17.  In particular, v8.99 is not
affected, though it doesn't support my camera really.

See the example:
https://bob.ipv.kfa-juelich.de/bronger/DSC06156.ARW
https://bob.ipv.kfa-juelich.de/bronger/DSC06156.tiff

** Affects: dcraw (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Raw color output fails with -h

Status in “dcraw” package in Ubuntu:
  New

Bug description:
  draw -T -h -o 0 DSC1.ARW

  produces a semi-transparent TIFF.  What I expect is a non-transparent
  TIFF with the quarter area of

  draw -T -o 0 DSC1.ARW

  I observe this bug in v9.16 and v9.17.  In particular, v8.99 is not
  affected, though it doesn't support my camera really.

  See the example:
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.ARW
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.tiff

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

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

[Desktop-packages] [Bug 1122833] Re: Raw color output fails with -h

2013-02-12 Thread Torsten Bronger

** Description changed:

- draw -T -h -o 0 DSC1.ARW
+ dcraw -T -h -o 0 DSC06156.ARW
  
  produces a semi-transparent TIFF.  What I expect is a non-transparent
  TIFF with the quarter area of
  
- draw -T -o 0 DSC1.ARW
+ dcraw -T -o 0 DSC06156.ARW
  
  I observe this bug in v9.16 and v9.17.  In particular, v8.99 is not
- affected, though it doesn't support my camera really.
+ affected, but it doesn't support my camera really.
  
  See the example:
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.ARW
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.tiff

** Summary changed:

- Raw color output fails with -h
+ Raw color setting produces semi-transparent TIFF with -h

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

Title:
  Raw color setting produces semi-transparent TIFF with -h

Status in “dcraw” package in Ubuntu:
  New

Bug description:
  dcraw -T -h -o 0 DSC06156.ARW

  produces a semi-transparent TIFF.  What I expect is a non-transparent
  TIFF with the quarter area of

  dcraw -T -o 0 DSC06156.ARW

  I observe this bug in v9.16 and v9.17.  In particular, v8.99 is not
  affected, but it doesn't support my camera really.

  See the example:
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.ARW
  https://bob.ipv.kfa-juelich.de/bronger/DSC06156.tiff

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

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

[Desktop-packages] [Bug 1074755] [NEW] Chromium not maximized after fullscreen

2012-11-03 Thread Torsten Bronger

Public bug reported:

Reproduced on Lubuntu 12.04 and Lubuntu 12.10.

Steps to reproduce:

1. Maximize Chromium e.g. with the second buttom in the top right corder of the 
window frame.
1. Switch Chromium to fullscreen with F11.
2. Switch back by pressing F11 again.

What I see:

Chromium's window is not maximized anymore.

What I expect:

The same status as after step (1), e.g. a maximised window.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: ubuntu = chromium-browser (Ubuntu)

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

Title:
  Chromium not maximized after fullscreen

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  Reproduced on Lubuntu 12.04 and Lubuntu 12.10.

  Steps to reproduce:

  1. Maximize Chromium e.g. with the second buttom in the top right corder of 
the window frame.
  1. Switch Chromium to fullscreen with F11.
  2. Switch back by pressing F11 again.

  What I see:

  Chromium's window is not maximized anymore.

  What I expect:

  The same status as after step (1), e.g. a maximised window.

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

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

[Desktop-packages] [Bug 871931] Re: ALT + circumflex can be set in the keybinding settings and conflict with unity

2011-10-26 Thread Torsten Bronger

This situation is very unfortunate for people using applications which
need Alt+^ because it cannot be switched off (as far as I can see).  I
use Emacs, where Alt+^ is an important functionality.  Besides, Alt+^ is
of little help on small keyboards with Fn key.

So please make the Unity keybinding configurable.

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

Title:
  ALT + circumflex can be set in the keybinding settings and conflict
  with unity

Status in Unity:
  New
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.10

  ALT + circumflex can be mapped in the keyboard settings despite
  being reserved for the new ALT + tab extended functionality, making it
  execute two functions at once with severe side effects (GUI freeze,
  but keys are still responsive - key smashing during freeze results in
  possible destruction of user data).

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

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

[Desktop-packages] [Bug 788996] Re: Firefox stops accepting characters while typing

2011-10-25 Thread Torsten Bronger

This problem probably has something to do with auto-completion.  It
causes the input to hang.  It's still a problem with FF7.

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

Title:
  Firefox stops accepting characters while typing

Status in “firefox” package in Ubuntu:
  New

Bug description:
  Binary package hint: firefox

  When I fill an input field in a web form, Firefox stops accepting
  further keystrokes after a couple of characters.  The same happens in
  the URL address line.  I have to re-click on the input field with the
  mouse, and then I can continue typing.

  While this seems to mean that the input field has lost focus, the
  cursor is still there.

  It doesn't happen with Textarea field, only with one-line input
  fields.

  I use Natty + Unity.

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

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

52 matches

Mail list logo