from:"Walter Lapchynski"

Given the above, I'm calling this fixed.

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

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

Title:
  bubble help flashes in libreoffice

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Hovering over any of the icons on the toolbar in libreoffice causes
  the bubble help to appear and disappear quickly.

  I'm attaching a video (mp4) of what I mean.

  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu0.18.10.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1813209/+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 1813209] Re: bubble help flashes in libreoffice

At least with the current settings of Lubuntu 19.04 and libreoffice-calc
1:6.2.2-0ubuntu2, I can confirm this is not an issue.

** Attachment added: "libreoffice tooltips working correctly"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1813209/+attachment/5255497/+files/libreoffice.webm

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

Title:
  bubble help flashes in libreoffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hovering over any of the icons on the toolbar in libreoffice causes
  the bubble help to appear and disappear quickly.

  I'm attaching a video (mp4) of what I mean.

  Version: 6.1.4.2
  Build ID: 1:6.1.4-0ubuntu0.18.10.1
  CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; 
  Locale: en-CA (en_CA.UTF-8); Calc: group threaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1813209/+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 1823917] Re: Can't set Chromium as the default browser when BROWSER variable is defined

I've also made the suggestion to LXQt to discontinue using `$BROWSER`
and instead using `xdg-settings` as I've shown how even though chromium
is unique in its robustness, there is still not a complete definition of
"default browser" (including dealing with file associations/mimetypes
and scheme handlers) by using `$BROWSER` alone, whereas `xdg-settings`
just resolves everything.

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

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
   1. Install firefox
   2. Set `BROWSER=firefox`
   3. Open firefox and make sure it is the default browser
   4. Install chromium-browser
   5. Open chromium-browser and set it as the default browser
   6. Click on a link or use `xdg-open URL`

  EXPECTED RESULTS
  Link opens in chromium-browser

  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.

  AFFECTED VERSIONS
  chromium-browser 73.0.3683.103-0ubuntu1

  UPSTREAM BUG REPORTS
  https://bugs.chromium.org/p/chromium/issues/detail?id=952569
  https://github.com/lxqt/lxqt/issues/1513#issuecomment-482779833

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1823917/+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 1823917] Re: Can't set Chromium as the default browser when BROWSER variable is defined

** Description changed:

  STEPS TO REPRODUCE
   1. Install firefox
   2. Set `BROWSER=firefox`
   3. Open firefox and make sure it is the default browser
   4. Install chromium-browser
   5. Open chromium-browser and set it as the default browser
   6. Click on a link or use `xdg-open URL`
  
  EXPECTED RESULTS
  Link opens in chromium-browser
  
  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.
  
  AFFECTED VERSIONS
  chromium-browser 73.0.3683.103-0ubuntu1
  
- UPSTREAM BUG REPORT
+ UPSTREAM BUG REPORTS
  https://bugs.chromium.org/p/chromium/issues/detail?id=952569
+ https://github.com/lxqt/lxqt/issues/1513#issuecomment-482779833

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

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
   1. Install firefox
   2. Set `BROWSER=firefox`
   3. Open firefox and make sure it is the default browser
   4. Install chromium-browser
   5. Open chromium-browser and set it as the default browser
   6. Click on a link or use `xdg-open URL`

  EXPECTED RESULTS
  Link opens in chromium-browser

  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.

  AFFECTED VERSIONS
  chromium-browser 73.0.3683.103-0ubuntu1

  UPSTREAM BUG REPORTS
  https://bugs.chromium.org/p/chromium/issues/detail?id=952569
  https://github.com/lxqt/lxqt/issues/1513#issuecomment-482779833

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1823917/+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 1823917] Re: Can't set Chromium as the default browser when BROWSER variable is defined

2019-04-12 Thread Walter Lapchynski

I will say, though, that there are many examples across various Linucies 
(that's the plural, right? ☺) suggesting to use the BROWSER variable to change 
the default browser. Case in point:
https://wiki.archlinux.org/index.php/Environment_Variables#Default_programs

And I might add another point: it's obvious that chromium-browser uses
`xdg-settings` but I'm not sure what firefox uses, but the end result is
that the `xdg-settings`, `xdg-mime` and `$BROWSER` values are all set
appropriately. I will note, too, that `xdg-settings` results in a
proportional change to `xdg-mime`.

I do think that setting BROWSER is problematic and it is contributing to
the problem, but the fact that chromium-browser seems to be unique among
other browsers in terms of lacking robustness to set itself as default
regardless of circumstances. Therefore, I think the fault lies with it.

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

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

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
   1. Install firefox
   2. Set `BROWSER=firefox`
   3. Open firefox and make sure it is the default browser
   4. Install chromium-browser
   5. Open chromium-browser and set it as the default browser
   6. Click on a link or use `xdg-open URL`

  EXPECTED RESULTS
  Link opens in chromium-browser

  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.

  AFFECTED VERSIONS
  chromium-browser 73.0.3683.103-0ubuntu1

  UPSTREAM BUG REPORT
  https://bugs.chromium.org/p/chromium/issues/detail?id=952569

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1823917/+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 1823917] Re: Can't set Chromium as the default browser when BROWSER variable is defined

2019-04-12 Thread Walter Lapchynski

** Description changed:

  STEPS TO REPRODUCE
-  1. Install firefox
-  2. Set `BROWSER=firefox`
-  3. Open firefox and make sure it is the default browser
-  4. Install chromium-browser
-  5. Open chromium-browser and set it as the default browser
-  6. Click on a link or use `xdg-open URL`
+  1. Install firefox
+  2. Set `BROWSER=firefox`
+  3. Open firefox and make sure it is the default browser
+  4. Install chromium-browser
+  5. Open chromium-browser and set it as the default browser
+  6. Click on a link or use `xdg-open URL`
  
  EXPECTED RESULTS
  Link opens in chromium-browser
  
  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.
  
+ AFFECTED VERSIONS
  chromium-browser 73.0.3683.103-0ubuntu1
+ 
+ UPSTREAM BUG REPORT
+ https://bugs.chromium.org/p/chromium/issues/detail?id=952569

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

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE
   1. Install firefox
   2. Set `BROWSER=firefox`
   3. Open firefox and make sure it is the default browser
   4. Install chromium-browser
   5. Open chromium-browser and set it as the default browser
   6. Click on a link or use `xdg-open URL`

  EXPECTED RESULTS
  Link opens in chromium-browser

  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.

  AFFECTED VERSIONS
  chromium-browser 73.0.3683.103-0ubuntu1

  UPSTREAM BUG REPORT
  https://bugs.chromium.org/p/chromium/issues/detail?id=952569

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1823917/+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 378783] Re: xdg-open *.desktop opens text editor

2019-04-12 Thread Walter Lapchynski

** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #54
   https://gitlab.gnome.org/GNOME/glib/issues/54

** Also affects: glib via
   https://gitlab.gnome.org/GNOME/glib/issues/54
   Importance: Unknown
   Status: Unknown

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

Title:
  xdg-open *.desktop opens text editor

Status in GLib:
  Unknown
Status in gvfs:
  New
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/378783/+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 1823917] Re: Can't set Chromium as the default browser when BROWSER variable is defined

2019-04-09 Thread Walter Lapchynski

** Description changed:

- Every time I launch the browser it suggests to be set as the default but if I 
click on that button nothing will change: I'll get the suggestion the next time 
I open Chromium, even if I reboot.
- Changing the default browser on configuration panel didn't solve the issue
+ STEPS TO REPRODUCE
+  1. Install firefox
+  2. Set `BROWSER=firefox`
+  3. Open firefox and make sure it is the default browser
+  4. Install chromium-browser
+  5. Open chromium-browser and set it as the default browser
+  6. Click on a link or use `xdg-open URL`
  
- Lubuntu 19.10 beta on Athlon 64x2 5200+
+ EXPECTED RESULTS
+ Link opens in chromium-browser
+ 
+ ACTUAL RESULTS
+ Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.
+ 
+ chromium-browser 73.0.3683.103-0ubuntu1

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

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE
   1. Install firefox
   2. Set `BROWSER=firefox`
   3. Open firefox and make sure it is the default browser
   4. Install chromium-browser
   5. Open chromium-browser and set it as the default browser
   6. Click on a link or use `xdg-open URL`

  EXPECTED RESULTS
  Link opens in chromium-browser

  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.

  chromium-browser 73.0.3683.103-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1823917/+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 1823917] Re: Can't set Chromium as the default browser

2019-04-09 Thread Walter Lapchynski

> xdg-settings: $BROWSER is set and can't be changed with xdg-settings

That's some telling info right there.

Some things to note:

 * In lxqt-config-session, in both Default Applications and Environment
(Advanced) there is an option to set the BROWSER variable. It is set to
firefox by default. It will come back if it is deleted (possibly a bug).
Unlike TERM or EDITOR, which are part of the UNIX standard
(http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_01),
BROWSER is not always recognized by applications.

 * There is a Freedesktop Specification for MIME types
(https://www.freedesktop.org/wiki/Specifications/mime-apps-spec/) that
lxqt-config-file-associations interacts with. The xdg-utils (XDG = X
Desktop Group, the former name of Freedesktop) tools interact with this.
You can use them to find out which is your default browser via `xdg-mime
query default text/html`. Similarly, `xdg-open` determines the MIME type
of the argument it is given and passes it to the associated application.

 * There is also update-alternatives which allows you to assign
different definitions of various types of generic programs. For example,
you could easily select from different definitions for x-www-browser. I
mention this for completeness, but it's not particularly relevant.

Now to prove this is not an issue with LXQt, consider this scenario:

 1. Load Lubuntu, which has firefox installed by default
 2. Install Opera
 3. Note that `echo $BROWSER` returns "firefox"
 4. Note that `xdg-mime query default text/html` returns "firefox.desktop"
 5. Note that `xdg-settings get default-web-browser` returns "firefox.desktop"
 6. Note `xdg-open http://ubuntu.com` opens in firefox
 7. Open qterminal and `echo 'http://ubuntu.com'`
 8. Note that holding down Ctrl and clicking on the URL opens it up in firefox
 9. Open up Opera and set it as the default browser
10. Note that `echo $BROWSER` returns "firefox"
11. Note that `xdg-mime query default text/html` returns "opera.desktop"
12. Note that `xdg-settings get default-web-browser` returns "opera.desktop"
13. Note `xdg-open http://ubuntu.com` opens in opera
14. Open qterminal and `echo 'http://ubuntu.com'`
15. Note that holding down Ctrl and clicking on the URL opens it up in opera

So why the problem with chromium-browser? Let's get back to that quote:

> xdg-settings: $BROWSER is set and can't be changed with xdg-settings

When you try to make chromium-browser default, it sees the BROWSER
variable and just gives up, whereas Opera (and Firefox) ignores it and
actually sets it. This error is actually from xdg-settings. It won't set
default-web-browser while BROWSER exists. Yet, somehow firefox and opera
both seem to deal with this. Therefore, I would call this chromium-
browser's fault.


** Package changed: lxqt-session (Ubuntu) => chromium-browser (Ubuntu)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- Can't set Chromium as the default browser
+ Can't set Chromium as the default browser when BROWSER variable is defined

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

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Every time I launch the browser it suggests to be set as the default but if I 
click on that button nothing will change: I'll get the suggestion the next time 
I open Chromium, even if I reboot.
  Changing the default browser on configuration panel didn't solve the issue

  Lubuntu 19.10 beta on Athlon 64x2 5200+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1823917/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

** Description changed:

- Some gkt2 applications randomly crash with same error. See attached
+ GTK2 applications randomly crash or freeze with same error. See attached
  files.

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  GTK2 applications randomly crash or freeze with same error. See
  attached files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1801161] Re: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

Oliver: there's a bug for pcmanfm
(https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984) with
the same end result. This seems to somehow related to GTK2, as there are
several other applications that show the same behavior
(https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710).
There's a file manager called SpaceFM one user tried and it showed the
problems with the GTK2 version but not with the GTK3 version. This,
coupled with Ilya's suggestion, leads me to believe GTK2 is indeed the
result. With pcmanfm, though there are specific behaviors that cause the
bug, it's not 100% reproducible. Sometimes those behaviors cause the
error and sometimes they do not.

However, Gérald's comment comes as something of a shock.

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

Title:
  soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion
  `!xcb_xlib_threads_sequence_lost' failed.

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Using LibreOffice Calc I was editing a filter on a pivot table and all
  LibreOffice windows hung.  What appeared in /var/log/syslog was:

  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown 
sequence number while processing queue
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely 
this is a multi-threaded client and XInitThreads has not been called
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry 
about that.
  Nov  1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: 
../../src/xcb_io.c:263: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  Nov  1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 
'WindowPreviewMenuItem' on the module 'windowPreview'. That property was 
defined with 'let' or 'const' inside the module. This was previously supported, 
but is not correct according to the ES6 standard. Any symbols to be exported 
from a module must be defined with 'var'. The property access will work as 
previously for the time being, but please fix your code anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-calc 1:6.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 13:39:03 2018
  InstallationDate: Installed on 2018-10-29 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

** Summary changed:

- !xcb_xlib_threads_sequence_lost error
+ !xcb_xlib_threads_sequence_lost error with GTK2 applications

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  Some gkt2 applications randomly crash with same error. See attached
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error

Related pcmanfm bug
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984

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

Title:
  !xcb_xlib_threads_sequence_lost error

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  Some gkt2 applications randomly crash with same error. See attached
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1799001] Re: Theming does not work on LXQt

2018-11-18 Thread Walter Lapchynski

** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Theming does not work on LXQt

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+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 1799001] Re: Theming does not work on LXQt

2018-11-18 Thread Walter Lapchynski

I can confirm this also functions correctly on Cosmic.

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

Title:
  Theming does not work on LXQt

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this change, LibreOffice does not correctly use the Breeze
  theme, which is needed for consistency with the rest of the Lubuntu,
  LXQt-based desktop. At times, it is even hard to use because of the
  inconsistent theming which can hide buttons at times.

  [Test Case]

  Update to the version of LibreOffice with this patch and open it on a
  Lubuntu 18.10 installation. It should use the Breeze theming rather
  than the stock GTK theming on startup.

  [Regression Potential]

  Little to none. If for some reason the criteria that is used to check
  for the LXQt desktop no longer works, which is unlikely in a stable
  release, this will no longer work.

  [Other Info]

  I submitted these upstream (as my first patches \o/):
  https://gerrit.libreoffice.org/61641
  https://gerrit.libreoffice.org/61751

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+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 1802674] Re: libgphoto2 builds lacks a link to the math library in all Ubuntu releases since at least Xenial 16.04

2018-11-11 Thread Walter Lapchynski

** Package changed: mtpaint (Ubuntu) => libgphoto2 (Ubuntu)

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

Title:
  libgphoto2 builds lacks a link to the math library in all Ubuntu
  releases since at least Xenial 16.04

Status in libgphoto2 package in Ubuntu:
  New

Bug description:
  Background:
  With all recent versions of GCC on GNU/Linux systems like Ubuntu, when you 
use the math library, you have to explicitly link to it.

  I am currently using Xenial 16.04 and did a recompile of source
  package libgphoto2. Then I got warnings fromdpkg-shlibdeps.

  make[1]: Entering directory 
'/home/ubuntu-xenial/user/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'
  dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/ptp2.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v 
to see them all)
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/stv0680.so 
contains an unresolvable reference to symbol pow: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sonix.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/jl2005c.so 
contains an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/digigr8.so 
contains an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/mars.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sierra.so 
contains an unresolvable reference to symbol roundf: it's probably a plugin
  make[1]: Leaving directory 
'/home/ubuntu-xenial/user/Downloads/Launchpad/libgphoto2/libgphoto2-2.5.9'

  I am quite sure that sqrt is the square root function from the math
  library. Usually, at least with GCC version newer than ~ 2013 you have
  to append a -lm to link against the math library. Obviously this isn't
  the case:

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. 
-I../libgphoto2_port -I../libgphoto2_port -D_GPHOTO2_INTERNAL_CODE 
-DLOCALEDIR=\"/usr/share/locale\" 
-DCAMLIBS=\"/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9\" -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libexif -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wmissing-declarations -Wmissing-prototypes -c gphoto2-filesys.c  -fPIC -DPIC 
-o .libs/libgphoto2_la-gphoto2-filesys.o
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. 
-I../libgphoto2_port -I../libgphoto2_port -D_GPHOTO2_INTERNAL_CODE 
-DLOCALEDIR=\"/usr/share/locale\" 
-DCAMLIBS=\"/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9\" -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libexif -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wmissing-declarations -Wmissing-prototypes -c gphoto2-filesys.c -fPIE -o 
libgphoto2_la-gphoto2-filesys.o >/dev/null 2>&1

  at the end we should see

  -c gphoto2-filesys.c -fPIE -lm -o libgphoto2_la-gphoto2-filesys.o
  >/dev/null 2>&1

  I did check in the official Ubuntu repository and you did get the same
  warnings:

  dh_shlibdeps -ldebian/libgphoto2-6/usr/lib/:debian/libgphoto2-port12/usr/lib/
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/jl2005c.so 
contains an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sierra.so 
contains an unresolvable reference to symbol roundf: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/ptp2.so contains 
an unresolvable reference to symbol log2: it's probably a plugin
  dpkg-shlibdeps: warning: 2 other similar warnings have been skipped (use -v 
to see them all)
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/digigr8.so 
contains an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/mars.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning: 
debian/libgphoto2-6/usr/lib/x86_64-linux-gnu/libgphoto2/2.5.9/sonix.so contains 
an unresolvable reference to symbol sqrt: it's probably a plugin
  dpkg-shlibdeps: warning:

[Desktop-packages] [Bug 1771615] Re: LibreOffice Apps do not appear in the panel taskbar

2018-10-13 Thread Walter Lapchynski

Sorry, but Lubuntu Next is not a released product as you can see from the list 
of Bionic images:
http://cdimage.ubuntu.com/lubuntu/releases/bionic/release/

There is no problem in the released image. There is also no problem in
Cosmic, which will be the first official release of Lubuntu with LXQt
when it is released this month.

** Changed in: libreoffice (Ubuntu)
   Status: New => Won't Fix

** Changed in: lxpanel (Ubuntu)
   Status: New => Won't Fix

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

Title:
  LibreOffice Apps do not appear in the panel taskbar

Status in libreoffice package in Ubuntu:
  Won't Fix
Status in lxpanel package in Ubuntu:
  Won't Fix

Bug description:
  I recently installed Lubuntu Next 18.04, which includes LibreOffice 6.

  At some point, I noticed that LibreOffice Writer (unlike all my other
  programs) does not appear in the panel's Taskbar (where all apps
  loaded in that workspace/desktop should be).

  All other apps with which I have experience, are listed in the taskbar, and 
can be minimized and un-minimized by clicking on the portion of the bar devoted 
to that app.
  There is an option in the panel settings that would allow me to only have 
apps appear in the taskbar when minimized, but I never use that.

  LibreOffice apps (I noticed this with Writer, but since tested it with
  the other LO apps that were installed with my OS, and the same thing
  happens with all) have nothing in the taskbar to show that they have
  opened, and when minimized, disappear entirely.

  I know that they have not quit when they disappear, in two ways:
  1. If I use the OS's menu to bring up LO-W again (thus with an blank 
document), and then go to that window's menu->Window, it shows all open LO-W 
documents, which can then be brought back by clicking on them.
  2.  Lubuntu Next's window manager OpenBox has a keyboard-shortcut Alt-Tab, 
which allows one to select from available app windows - and at least one LO 
document is listed, from which the others can then be accessed by #1.

  I don't know what causes an app to have windows in the taskbar, but that 
system is failing with LO windows.
  (I guess that I had assumed that the OS took care of managing windows in the 
taskbar - having them appear there when opened, and removing them when closed), 
but apparently I am wrong, or LO windows would not be able to hide, as they 
seem to do...)

  I am assuming that this is a new bug, as this did not happen before.
  I cannot think that it is a design decision, not to let the user minimize 
documents (or simultaneously open multiple documents) without apparently losing 
them altogether (at least without jumping through hoops (hoops of which they 
might well not be aware...)).

  

  scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
  Linux scott-ASUS-M2N68-AM-PLUS 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 
06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc
  Ubuntu 18.04 LTS
  bionic
  scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
  QLubuntu

  scott@scott-ASUS-M2N68-AM-PLUS:~$ apt-cache policy libreoffice-core
  libreoffice-core:
Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Wed May 16 11:22:53 2018
  InstallationDate: Installed on 2018-04-29 (16 days ago)
  InstallationMedia: Lubuntu-Next 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2018-09-10 Thread Walter Lapchynski

bodhi, having the Technical Board review Phillip's posts might be
completely reasonable so as to finally end this conversation once and
for all. That has no bearing on the moderation, though.

The entire Ubuntu Community is bound by the terms of the Code of
Conduct, which, in short, means being nice to one another, regardless of
our points of view. So, I'm sorry, you don't just get to treat people
however you want just because you disagree with them. There is no
moderation as it concerns your attempts to correct a confusing technical
situation. Where the moderation exists is where it no longer remains
technical and especially where it becomes a personal attack.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting

[Desktop-packages] [Bug 1789071]

2018-08-27 Thread Walter Lapchynski

One more thing. The corrected version is actually in proposed:
https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati/1:18.0.1-2

I do not recommend enabling proposed in general, especially for
something so crucial to the whole system. However, since it seems you're
doing testing and not on a production system, it might be worthwhile to
enable proposed and get the likely solution:
https://wiki.ubuntu.com/Testing/EnableProposed

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

Title:
  Invalid command stream with Radeon driver

Status in Lubuntu Artwork:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Fix Committed

Bug description:
  Lubuntu 18.10 daily 08-25

  I have a Pentium 4 SL7E8, 512 MB of RAM in a PT800CE-A from ECS and an
  ATI Radeon HD 4650 on AGP.

  The live CD boots up well to the Desktop, but then when I open an
  application, the part of the screen where the application should be
  hides the mouse cursor when I hover it, the Desktop background picture
  remains.

  Pressing screen 2, 3, 4 the hovering cursor is not hidden any more and
  pressing screen 1 the cursor is hidden again.

  When pressing screen 2, 3, 4 the screen button indicator remains on 1.

  I did a CTRL+ALT+F2 and lubuntu ENTER and:

  dmesg |tail -50

  made a photo with my phone and attached it here.

  I am ready to run other commands you want after boot and attach the
  photo of the output here.

  I am sorry if this is not the right place for this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-artwork/+bug/1789071/+subscriptions

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2018-08-20 Thread Walter Lapchynski

Phillip and bodhi, I know this is something we have discussed before,
but I'm going to say it again and hopefully for the last time: please
keep your comments civil. You can disagree with each other all you want,
but do it respectfully, please. If you see yourself using the word "you"
(or if it's implied) in a comment, that's a sign you're probably doing
something wrong.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME

[Desktop-packages] [Bug 685596] Re: users-admin doesn't report error when PolicyKit authentication fails

2018-04-28 Thread Walter Lapchynski

I cannot replicate this in Bionic, at least if I understand the steps to
reproduce correctly. If this is still valid in Bionic, please re-write
the description with clear steps to reproduce. Ideally, this should be
something that could be recreated from a fresh install. Thanks!

** Changed in: gnome-system-tools (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  users-admin doesn't report error when PolicyKit authentication fails

Status in gnome-system-tools package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gnome-system-tools

  When I run users-admin (gnome-system-tools package version
  2.32.0-0ubuntu1) in natty i386, clicking the "Add", "Delete", and
  "Advanced Settings" buttons has no effect. Clicking the "Manage
  Groups" button does bring up the "Groups settings" window.

  In the "Groups settings" window, the "Add" and "Delete" buttons have
  no effect. Clicking the "Properties" button does bring up the Group
  Properties window for the selected group.

  In the Group Properties window, changing the group ID to a number
  already in use by another group does issue an error, but changing the
  group ID number to a number not already in use or changing which users
  are members of the group fail silently (as though the operations had
  succeeded).

  When I run users-admin from a console, it prints this output to the
  command-line upon launch:

  GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings
  will not be saved or shared with other applications.

  (users-admin:1337): GLib-GObject-CRITICAL **: g_object_unref:
  assertion `G_IS_OBJECT (object)' failed

  Clicking the "Manage Groups" button results in another assertion
  message being printed (every time it is clicked). Clicking other
  buttons mentioned above does not result in messages being printed.

  When I first experienced this bug, my system suffered from Bug 685349.
  I had thought that might have been the cause of this bug (though in
  hindsight I am not sure why I thought that). As a workaround for Bug
  685349, I manually changed the value of the gconf2 key /apps/gksu
  /sudo-mode key from false to true. This fixed my problems elevating
  privileges to root in other applications, including other gnome-
  system-tools applications, but it did not appear to have any effect on
  the behavior of users-admin, including its output to the console. I
  bring this up to suggest that this bug in users-admin is occurring
  before any attempt is made to elevate privileges to root (or
  preventing such an attempt from being made).

  (This bug is the "situation" I referred to in Bug 685215 that had led
  me to try running users-admin as root.)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-system-tools 2.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.37-7.19-generic 2.6.37-rc3
  Uname: Linux 2.6.37-7-generic i686
  Architecture: i386
  Date: Sun Dec  5 13:10:22 2010
  ExecutablePath: /usr/bin/users-admin
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101202)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  SourcePackage: gnome-system-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/685596/+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 607999] Re: gsettings-data-convert crashed with signal 5 in g_object_newv()

2018-04-28 Thread Walter Lapchynski

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Beyond that, I have not seen a bug likes this in many years. If you
could provide additional information on how it affects a currently
supported release, that would be most helpful.

** Changed in: gconf (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  gsettings-data-convert crashed with signal 5 in g_object_newv()

Status in gconf:
  New
Status in gconf package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gconf

  got this after running updates in maverick

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: gconf2 2.31.6-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
  Uname: Linux 2.6.35-8-generic x86_64
  Architecture: amd64
  Date: Tue Jul 20 23:56:30 2010
  ExecutablePath: /usr/bin/gsettings-data-convert
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100605)
  ProcCmdline: gsettings-data-convert
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gconf
  StacktraceTop:
   ?? () from /usr/lib/libgio-2.0.so.0
   ?? () from /usr/lib/libgio-2.0.so.0
   g_object_newv () from /usr/lib/libgobject-2.0.so.0
   g_object_new_valist ()
   g_object_new () from /usr/lib/libgobject-2.0.so.0
  Title: gsettings-data-convert crashed with signal 5 in g_object_newv()
  UserGroups:

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-12-11 Thread Walter Lapchynski

We need to talk about software here, not personal issues. You both are
going to stop attacking each other, defending yourself against each
other, and talk about software. If you cannot talk about the software
without getting these other issues intermingled here, do not comment at
all.

Since you seem to be concerned about the user experience, please
recognize the user experience for all the people looking at this bug
reports. Be nice.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion:

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-12-08 Thread Walter Lapchynski

Again: let's keep any further discussion about people directed towards
community-coun...@lists.ubuntu.com and let's keep the bug report for
talking about the actual software. In other words, no more comments
about the CoC violations in this bug report. Let's get back to talking
about the software.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  New
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

2017-12-08 Thread Walter Lapchynski

Speaking as a member of the Ubuntu Community Council, I'm going to have
to ask that we dial down the tone here. As you know, the Code of Conduct
(https://www.ubuntu.com/about/about-ubuntu/conduct) means that we should
act with respect and consideration, act collaboratively and work towards
consensus and clarity. That's sadly not what I'm seeing in this
discussion and we need to put an end to it.

I will also comment that if anyone sees a violation of this, the
appropriate action is not to escalate the language, but to take it down
a notch. If you don't feel like you can do that, that's what the
Community Council is for. Discussing someone's personal history publicly
not to mention speculating about someone's medical conditions, however
appropriate it is in regards to a violation of the CoC, is not in any
way respectful or considerate.

That said, let's keep any further discussion about people directed
towards community-coun...@lists.ubuntu.com and let's keep the bug report
for talking about the actual software.

Speaking of the bug, some things to point out:

 1. I note that this is a known issue in the 17.10 release 
(https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#Desktop) with a note 
suggesting that Fedora is the upstream. That said, if the problem is an issue 
of upstream Wayland security policy, then, this is a bug report that should be 
filed upstream. In other words, it is not an Ubuntu problem.
 2. If the issue is how Ubuntu deals with this, there are currently several 
documented workaround to fixing the problem as above, and it's clear that other 
work is being done (PolicyKit, admin URIs, etc.) to try to solve this problem 
once and for all.

Thank you all.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  New
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink

Re: [Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever

2017-03-29 Thread Walter Lapchynski

Ok but can it be less than 500 files? What's the minimum? What versions does 
this NOT happen on? 
--
   @wxl | polka.bike
C563 CAC5 8BE1 2F22 A49D
68F6 8B57 A48B C4F2 051A

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Incomplete
Status in pcmanfm package in Ubuntu:
  Incomplete

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1133477/+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 1133477] Re: cut-n-paste move files got stuck forever

2017-03-28 Thread Walter Lapchynski

I see no clear test case bug triagers can try to do further research on.
I have no information from syslog, dmesg, or any tracing or anything. Is
this only with images? What's the minimum number or size? I would this
this has something to do with a generic Backend, so we should look for
conditions that are universal across all file managers. Please provide
this so we can continue researching. If there's no clear way to
reproduce, no matter how often this happen or how long it's reported, we
cannot fix this.

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: pcmanfm (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Incomplete
Status in pcmanfm package in Ubuntu:
  Incomplete

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1133477/+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 1617777] Re: HPLIP applet does not show window when clicking on it

2016-08-29 Thread Walter Lapchynski

Some version information would be helpful, too.

** No longer affects: lubuntu-next

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

Title:
  HPLIP applet does not show window when clicking on it

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  The taskbar applet for HP printers does not show an information window
  when its icon is pressed – the icon is briefly highlighted and nothing
  else happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/161/+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 1575803] Re: firefox print dialog selects print to file when selecting a non-default printer

2016-04-27 Thread Walter Lapchynski

** Description changed:

  STEPS TO REPRODUCE
-  1. Open the print dialog with e.g. File → Print or (hamburger icon) → Print 
→ Print
-  2. Select a non-default printer
-  3. Select one of the tabs in the dialog, e.g. Page Setup
+  1. Open the print dialog with e.g. File → Print or (hamburger icon) → Print 
→ Print
+  2. Select a non-default printer
+  3. Select one of the tabs in the dialog, e.g. Page Setup
  
  EXPECTED RESULTS
  The tab is opened for the selected printer.
  
  ACTUAL RESULTS
  The Print to File printer is selected and does not open the tab. The other 
tabs available in other printers (but not in this virtual printer for Print to 
File) are missing. Continuing to print will attempt to print to file.
  
  AFFECTS
-  * firefox 46.0+build5-0ubuntu0.14.04.2
+  * firefox 46.0+build5-0ubuntu0.14.04.2
  
  WORKAROUND
-  1. After the Print to File printer is selected, click the Page Setup or 
Options tabs
-  2. Change options as needed
-  3. Select the General tab
-  4. Reselect the right printer and those settings will be applied
+  1. After the Print to File printer is selected, click the Page Setup or 
Options tabs
+  2. Change options as needed
+  3. Select the General tab
+  4. Reselect the right printer and those settings will be applied
  …but note that you can't change anything on other tabs.
+  * or install Aurora from the Mozilla Build Team's PPA: 
https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/firefox-aurora
  
  NOTES
-  * 20 April, I received an update to 45.0.2+build1-0ubuntu0.14.04.1, which 
was unaffected. There have been no other updates since.
-  * This is on i386 Kubuntu, but neither fact should be relevant.
+  * 20 April, I received an update to 45.0.2+build1-0ubuntu0.14.04.1, which 
was unaffected. There have been no other updates since.
+  * 47.0~a2~hg20160412r310537-0ubuntu1~umd1~trusty (Aurora) is unaffected
+  * This is on i386 Kubuntu, but neither fact should be relevant.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 46.0+build5-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 4.2.0-34.39~14.04.1-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  wxl   10651 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  wxl   10651 F pulseaudio
  BuildID: 20160425115337
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Apr 27 10:23:16 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2013-05-14 (1078 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  IpRoute:
-  default via 10.23.1.1 dev eth1  proto static 
-  10.23.1.0/24 dev eth1  proto kernel  scope link  src 10.23.1.236  metric 1 
-  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
+  default via 10.23.1.1 dev eth1  proto static
+  10.23.1.0/24 dev eth1  proto kernel  scope link  src 10.23.1.236  metric 1
+  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  IwConfig:
-  eth1  no wireless extensions.
-  
-  virbr0no wireless extensions.
-  
-  lono wireless extensions.
+  eth1  no wireless extensions.
+ 
+  virbr0no wireless extensions.
+ 
+  lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-0c2bf835-4be0-4e41-9cc7-9808d2150512
  Plugins:
-  Skype Buttons for Kopete - /usr/lib/mozilla/plugins/skypebuttons.so (kopete)
-  IcedTea-Web Plugin (using IcedTea-Web 1.5.3 (1.5.3-0ubuntu0.14.04.1)) - 
/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so 
(icedtea-7-plugin)
-  Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
+  Skype Buttons for Kopete - /usr/lib/mozilla/plugins/skypebuttons.so (kopete)
+  IcedTea-Web Plugin (using IcedTea-Web 1.5.3 (1.5.3-0ubuntu0.14.04.1)) - 
/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so 
(icedtea-7-plugin)
+  Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=46.0/20160425115337 (In use)
  RelatedPackageVersions:
-  kopete   4:4.14.3-0ubuntu1~ubuntu14.04~ppa2
-  icedtea-7-plugin 1.5.3-0ubuntu0.14.04.1
+  kopete   4:4.14.3-0ubuntu1~ubuntu14.04~ppa2
+  icedtea-7-plugin 1.5.3-0ubuntu0.14.04.1
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  RunningIncompatibleAddons: False

[Desktop-packages] [Bug 1575803] [NEW] firefox print dialog selects print to file when selecting a non-default printer

2016-04-27 Thread Walter Lapchynski

Public bug reported:

STEPS TO REPRODUCE
 1. Open the print dialog with e.g. File → Print or (hamburger icon) → Print → 
Print
 2. Select a non-default printer
 3. Select one of the tabs in the dialog, e.g. Page Setup

EXPECTED RESULTS
The tab is opened for the selected printer.

ACTUAL RESULTS
The Print to File printer is selected and does not open the tab. The other tabs 
available in other printers (but not in this virtual printer for Print to File) 
are missing. Continuing to print will attempt to print to file.

AFFECTS
 * firefox 46.0+build5-0ubuntu0.14.04.2

WORKAROUND
 1. After the Print to File printer is selected, click the Page Setup or 
Options tabs
 2. Change options as needed
 3. Select the General tab
 4. Reselect the right printer and those settings will be applied
…but note that you can't change anything on other tabs.

NOTES
 * 20 April, I received an update to 45.0.2+build1-0ubuntu0.14.04.1, which was 
unaffected. There have been no other updates since.
 * This is on i386 Kubuntu, but neither fact should be relevant.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 46.0+build5-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 4.2.0-34.39~14.04.1-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  wxl   10651 F pulseaudio
BuildID: 20160425115337
Channel: Unavailable
CurrentDesktop: KDE
Date: Wed Apr 27 10:23:16 2016
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2013-05-14 (1078 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
IpRoute:
 default via 10.23.1.1 dev eth1  proto static 
 10.23.1.0/24 dev eth1  proto kernel  scope link  src 10.23.1.236  metric 1 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
IwConfig:
 eth1  no wireless extensions.
 
 virbr0no wireless extensions.
 
 lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-0c2bf835-4be0-4e41-9cc7-9808d2150512
Plugins:
 Skype Buttons for Kopete - /usr/lib/mozilla/plugins/skypebuttons.so (kopete)
 IcedTea-Web Plugin (using IcedTea-Web 1.5.3 (1.5.3-0ubuntu0.14.04.1)) - 
/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so 
(icedtea-7-plugin)
 Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=46.0/20160425115337 (In use)
RelatedPackageVersions:
 kopete   4:4.14.3-0ubuntu1~ubuntu14.04~ppa2
 icedtea-7-plugin 1.5.3-0ubuntu0.14.04.1
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
 bp-0c2bf835-4be0-4e41-9cc7-9808d2150512
 bp-170302ae-8534-430b-843c-5b3d62150403
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to trusty on 2015-02-20 (432 days ago)
dmi.bios.date: 07/21/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F1 v01.32
dmi.board.asset.tag: 2UA8250JJQ
dmi.board.name: 0AA8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA8250JJQ
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.32:bd07/21/2011:svnHewlett-Packard:pnHPCompaqdc7800SmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP Compaq dc7800 Small Form Factor
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-bug i386 print trusty

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

Title:
  firefox print dialog selects print to file when selecting a non-
  default printer

Status in firefox package in Ubuntu:
  New

Bug description:
  STEPS TO REPRODUCE
   1. Open the print dialog with e.g. File → Print or (hamburger icon) → Print 
→ Print
   2. Select a non-default printer
   3. Select one of the tabs in the dialog, e.g. Page Setup

  EXPECTED RESULTS
  The tab is opened for the selected printer.

  ACTUAL RESULTS
  The Print to File printer is selected and does not open the tab. The other 
tabs available in other printers (but not in this virtual printer for Print to 
File) are missing. Continuing to print will attempt to print to file.

  AFFECTS
   * firefox 46.0+build5-0ubuntu0.14.04.2

  WORKAROUND
   1. After the Print to File printer is selected, click the Page Setup or 
Options tabs
   2. Change options as needed
   3. Select the General tab
   4. Reselect the right printer and those

[Desktop-packages] [Bug 1547793] Re: upowerd crashed with SIGSEGV in g_variant_is_trusted()

2016-02-27 Thread Walter Lapchynski

@jiaowen520li, please tell me you're not seeing this problem still in
Beta2.

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

Title:
  upowerd crashed with SIGSEGV in g_variant_is_trusted()

Status in Ubuntu Kylin:
  New
Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in upower package in Debian:
  Fix Released

Bug description:
  Crash when connecting laptop to charger.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: upower 0.99.4-1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Feb 20 16:18:04 2016
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2015-04-07 (319 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fdb12e38ee0:mov0x20(%rdi),%eax
   PC (0x7fdb12e38ee0) ok
   source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: upowerd crashed with SIGSEGV in g_variant_builder_add_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1547793/+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 1530323] Re: The input box for editing a Wired connection static IP address doesn't appear correctly

2016-01-30 Thread Walter Lapchynski

Moved to high as it makes it impossible for anyone to enter the IP
address. It's not just a visual glitch. It's unusable.

** Changed in: network-manager-applet (Ubuntu)
   Importance: Low => High

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

Title:
  The input box for editing a Wired connection static IP address doesn't
  appear correctly

Status in Lubuntu default settings:
  New
Status in ubuntu-mate:
  Confirmed
Status in Ubuntu Kylin:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Configuration:
  PC: Dell-Vostro-260s
  OS: UK16.04-1230-Daily-amd64
  APP: network-manager-gnome

  The input box for IP doesn't appear correctly in the edit window of
  Wired connection.

  在有线网络连接编辑页面进行手动配置网络时，IP地址设置栏由于输入框过大，输入过程中无法显示全键入数字，最大化后可正常查看。

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1530323/+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 1434108] Re: Error exporting Libre Writer file to PDF

2015-12-13 Thread Walter Lapchynski

This is not Lubuntu specific as far as I can tell, so I'm unsubscribing
Lubuntu Packages Team.

Also, this only happens with that specific commerical font? Could it
perhaps be an issue with the font itself?

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

Title:
  Error exporting Libre Writer file to PDF

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Steps to Reproduce:
  1) Open Libre Writer and create a new document

  2) Type something using the 'TheMix' font from
  http://www.lucasfonts.com/fonts/themix/themix

  3) Export file as PDF.

  Expected Results:
  - The Libre Writer document should be identically reproduced in PDF format. 
Characters should be in the same place.

  Actual Results:
  - In the PDF file, some characters are shifted together. Other characters 
such as capital letters are replaced by question marks. 

  Notes:

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libreoffice-core 1:4.4.1-0ubuntu1
  Font: http://www.lucasfonts.com/fonts/themix/themix

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1434108/+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 1434108] Re: Error exporting Libre Writer file to PDF

2015-12-13 Thread Walter Lapchynski

** Description changed:

  Steps to Reproduce:
  1) Open Libre Writer and create a new document
- 
- 2) Type something using the 'TheMix' font from
- http://www.lucasfonts.com/fonts/themix/themix
- 
+ 2) Type something using the 'TheMix' font from 
http://www.lucasfonts.com/fonts/themix/themix
  3) Export file as PDF.
  
  Expected Results:
  - The Libre Writer document should be identically reproduced in PDF format. 
Characters should be in the same place.
  
  Actual Results:
- - In the PDF file, some characters are shifted together. Other characters 
such as capital letters are replaced by question marks. 
+ - In the PDF file, some characters are shifted together. Other characters 
such as capital letters are replaced by question marks.
  
  Notes:
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 15.04
- Package: libreoffice-core 1:4.4.1-0ubuntu1
- Font: http://www.lucasfonts.com/fonts/themix/themix
+ Confirmed with: 
+  * Ubuntu 15.04/libreoffice 1:4.4.1-0ubuntu1
+ Unconfirmed with:
+  * 14.04/1:4.2.7-0ubuntu2
+  * 15.10/1:5.0.1-0ubuntu1

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

Title:
  Error exporting Libre Writer file to PDF

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Steps to Reproduce:
  1) Open Libre Writer and create a new document
  2) Type something using the 'TheMix' font from 
http://www.lucasfonts.com/fonts/themix/themix
  3) Export file as PDF.

  Expected Results:
  - The Libre Writer document should be identically reproduced in PDF format. 
Characters should be in the same place.

  Actual Results:
  - In the PDF file, some characters are shifted together. Other characters 
such as capital letters are replaced by question marks.

  Notes:
  Confirmed with: 
   * Ubuntu 15.04/libreoffice 1:4.4.1-0ubuntu1
  Unconfirmed with:
   * 14.04/1:4.2.7-0ubuntu2
   * 15.10/1:5.0.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1434108/+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 1510709] Re: In Wily some GTK related packages pull many additional packages

2015-10-28 Thread Walter Lapchynski

** Package changed: obconf (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- In Wily some GTK related packages pull many additional packages
+ In Wily GTK libs depend upon additional packages relative to Vivid

** Tags removed: dependencies issue
** Tags added: depends vivid xenial

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  In Wily GTK libs depend upon additional packages relative to Vivid

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I start building a minimalist install with Openbox and I meet with the
  following issues:

  WITH RECOMMENDS TURNED OFF (it should not bring in anything, except
  probably some gtk+2 libraries? (
  http://openbox.org/wiki/ObConf:About#Dependencies ).

  Here is what it wants to install:
  
  root@pourpier:~# apt-get install obconf
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    adwaita-icon-theme dconf-gsettings-backend dconf-service glib-networking
    glib-networking-common glib-networking-services gsettings-desktop-schemas
    hicolor-icon-theme humanity-icon-theme libatk-bridge2.0-0 libatk1.0-0
    libatk1.0-data libatspi2.0-0 libboost-filesystem1.58.0 libboost-system1.58.0
    libcairo-gobject2 libcolord2 libdconf1 libdrm-amdgpu1 libdrm-intel1
    libdrm-nouveau2 libdrm-radeon1 libegl1-mesa libepoxy0 libgbm1 
libgl1-mesa-dri
    libgtk-3-0 libgtk-3-bin libgtk-3-common libjson-glib-1.0-0
    libjson-glib-1.0-common liblcms2-2 libllvm3.6v5 libmirclient9 libmircommon5
    libmirprotobuf3 libpciaccess0 libprotobuf-lite9v5 libproxy1v5 librest-0.7-0
    librsvg2-common libsoup-gnome2.4-1 libsoup2.4-1 libwayland-client0
    libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libxcb-dri2-0
    libxcb-xfixes0 libxcomposite1 libxcursor1 libxdamage1 libxfixes3
    libxkbcommon0 ubuntu-mono
  Suggested packages:
    gvfs liblcms2-utils
  Recommended packages:
    at-spi2-core colord libtxc-dxtn-s2tc0 libtxc-dxtn0
  The following NEW packages will be installed:
    adwaita-icon-theme dconf-gsettings-backend dconf-service glib-networking
    glib-networking-common glib-networking-services gsettings-desktop-schemas
    hicolor-icon-theme humanity-icon-theme libatk-bridge2.0-0 libatk1.0-0
    libatk1.0-data libatspi2.0-0 libboost-filesystem1.58.0 libboost-system1.58.0
    libcairo-gobject2 libcolord2 libdconf1 libdrm-amdgpu1 libdrm-intel1
    libdrm-nouveau2 libdrm-radeon1 libegl1-mesa libepoxy0 libgbm1 
libgl1-mesa-dri
    libgtk-3-0 libgtk-3-bin libgtk-3-common libjson-glib-1.0-0
    libjson-glib-1.0-common liblcms2-2 libllvm3.6v5 libmirclient9 libmircommon5
    libmirprotobuf3 libpciaccess0 libprotobuf-lite9v5 libproxy1v5 librest-0.7-0
    librsvg2-common libsoup-gnome2.4-1 libsoup2.4-1 libwayland-client0
    libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libxcb-dri2-0
    libxcb-xfixes0 libxcomposite1 libxcursor1 libxdamage1 libxfixes3
    libxkbcommon0 obconf ubuntu-mono
  0 upgraded, 56 newly installed, 0 to remove and 0 not upgraded.
  Need to get 19.6 MB of archives.
  After this operation, 187 MB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.
  root@pourpier:~#

  *

  In case anyone would have doubts about the recommends turned off in the 
99synaptic file:
  *
  root@pourpier:~# apt-get install --no-install-recommends obconf
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
    adwaita-icon-theme dconf-gsettings-backend dconf-service glib-networking
    glib-networking-common glib-networking-services gsettings-desktop-schemas
    hicolor-icon-theme humanity-icon-theme libatk-bridge2.0-0 libatk1.0-0
    libatk1.0-data libatspi2.0-0 libboost-filesystem1.58.0 libboost-system1.58.0
    libcairo-gobject2 libcolord2 libdconf1 libdrm-amdgpu1 libdrm-intel1
    libdrm-nouveau2 libdrm-radeon1 libegl1-mesa libepoxy0 libgbm1 
libgl1-mesa-dri
    libgtk-3-0 libgtk-3-bin libgtk-3-common libjson-glib-1.0-0
    libjson-glib-1.0-common liblcms2-2 libllvm3.6v5 libmirclient9 libmircommon5
    libmirprotobuf3 libpciaccess0 libprotobuf-lite9v5 libproxy1v5 librest-0.7-0
    librsvg2-common libsoup-gnome2.4-1 libsoup2.4-1 libwayland-client0
    libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libxcb-dri2-0
    libxcb-xfixes0 libxcomposite1 libxcursor1 libxdamage1 libxfixes3
    libxkbcommon0 ubuntu-mono
  Suggested packages:
    gvfs liblcms2-utils
  Recommended packages:
    at-spi2-core colord libtxc-dxtn-s2tc0 libtxc-dxtn0
  The following NEW packages will be installed:
    adwaita-icon-theme dconf-gsettings-backend

[Desktop-packages] [Bug 1430358] Re: lubuntu crash on start

2015-08-14 Thread Walter Lapchynski

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

** This bug has been marked a duplicate of bug 1450785
   X server fails to start on Lubuntu Vivid desktop

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

Title:
  lubuntu crash on start

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  lubuntu start with black screen.

  Now I can't log in to Lubuntu enviroment. When i try to log in massage is 
showede:
  Starting version 219
  [ OK ] Started Light Display Manager.
  and the loging screen si showed again.

   In past booting up is slow but i was able to log in.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432681

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: i386
  Date: Tue Mar 10 12:41:44 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-03-16 (724 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 
-nolisten tcp vt8 -novtswitch
  ProcEnviron:

  Signal: 6
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to vivid on 2015-02-27 (10 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1430358/+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 1430358]

2015-08-12 Thread Walter Lapchynski

Is this not the same problem you described in the other bug you recently
made?

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

Title:
  lubuntu crash on start

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  lubuntu start with black screen.

  Now I can't log in to Lubuntu enviroment. When i try to log in massage is 
showede:
  Starting version 219
  [ OK ] Started Light Display Manager.
  and the loging screen si showed again.

   In past booting up is slow but i was able to log in.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432681

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: i386
  Date: Tue Mar 10 12:41:44 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-03-16 (724 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 
-nolisten tcp vt8 -novtswitch
  ProcEnviron:

  Signal: 6
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to vivid on 2015-02-27 (10 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1430358/+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 964705] Re: System policy prevents modification of network settings for all users

2015-06-29 Thread Walter Lapchynski

Mathieu, it doesn't seem that the upstream fix in Debian ever got merged
into Ubuntu. Is there a reason for this?

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

Title:
  System policy prevents modification of network settings for all users

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Fix Released
Status in network-manager package in openSUSE:
  Fix Released

Bug description:
  This seems like a regression? The screen shot is at
  http://thesii.org/Screenshot.jpg The nearest link I can find is from
  the forum area at http://ubuntuforums.org/showthread.php?p=1146

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Mar 25 19:36:45 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Alpha amd64 (20120323)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/964705/+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 1452272] Re: Cut/Copy/Paste/Select All are active while they shouldn't

2015-05-08 Thread Walter Lapchynski

Barring the above information, the rest should be incomplete.

** Changed in: filezilla (Ubuntu)
   Status: New = Incomplete

** Changed in: gimp (Ubuntu)
   Status: New = Incomplete

** Changed in: libreoffice (Ubuntu)
   Status: New = Incomplete

** Changed in: lxdm (Ubuntu)
   Status: New = Incomplete

** Changed in: lxpanel (Ubuntu)
   Status: New = Incomplete

** Changed in: lxterminal (Ubuntu)
   Status: New = Incomplete

** Changed in: pcmanfm (Ubuntu)
   Status: New = Incomplete

** Changed in: pidgin (Ubuntu)
   Status: New = Incomplete

** Changed in: scite (Ubuntu)
   Status: New = Incomplete

** Changed in: xscreensaver (Ubuntu)
   Status: New = Incomplete

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

Title:
  Cut/Copy/Paste/Select All are active while they shouldn't

Status in filezilla package in Ubuntu:
  Incomplete
Status in gimp package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Incomplete
Status in lxdm package in Ubuntu:
  Incomplete
Status in lxpanel package in Ubuntu:
  Incomplete
Status in lxterminal package in Ubuntu:
  Incomplete
Status in pcmanfm package in Ubuntu:
  Incomplete
Status in pidgin package in Ubuntu:
  Incomplete
Status in scite package in Ubuntu:
  Incomplete
Status in xscreensaver package in Ubuntu:
  Incomplete

Bug description:
  I have already created a few upstream reports for this but since
  nearly every application on my system (Ubuntu 15.04) is affected by
  this issue and I'm getting tired of opening this many upstream reports
  I'm creating this collecting ticket.

  To the issue: Commonly at least one of this happens if the related
  context menu (commonly in the menu bar - Edit or with a right mouse
  click on a related field) gets opened:

  - Cut/Copy are active while nothing is selected.
  - Paste is active while nothing is in the clipboard.
  - Select All is active while the related field is empty.

  Here are the upstream reports which I have already created:

  LibreOffice: https://bugs.documentfoundation.org/show_bug.cgi?id=91107
  SciTE: http://sourceforge.net/p/scintilla/bugs/1718/
  GIMP: https://bugzilla.gnome.org/show_bug.cgi?id=749002

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/filezilla/+bug/1452272/+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 1430358] Re: lubuntu crash on start

2015-04-16 Thread Walter Lapchynski

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

** This bug is no longer a duplicate of bug 1434220
   lubuntu crash on start
** This bug has been marked a duplicate of bug 1424362
   permissions issues in LXDE as of Vivid Lubuntu Final Beta

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

Title:
  lubuntu crash on start

Status in xorg-server package in Ubuntu:
  New

Bug description:
  lubuntu start with black screen.

  Now I can't log in to Lubuntu enviroment. When i try to log in massage is 
showede:
  Starting version 219
  [ OK ] Started Light Display Manager.
  and the loging screen si showed again.

   In past booting up is slow but i was able to log in.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432681

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: i386
  Date: Tue Mar 10 12:41:44 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-03-16 (724 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 
-nolisten tcp vt8 -novtswitch
  ProcEnviron:

  Signal: 6
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to vivid on 2015-02-27 (10 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1430358/+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 1442406] Re: Can't unlock UMTS modem with PIN

2015-04-15 Thread Walter Lapchynski

If you use the workaround at #1424362:

WORKAROUND
 1. open Default Apps for LXSession
 2. click on autostart tab
 3. make sure PolicyKit Authentication Agent is checked
 * NOTE: works on a per user basis

…is this fixed?

If so, please mark it as a dupe.

If it is not, then we need some more information. Specifically, I would
like to know if this affects any other network manager tasks and if so,
which. I'd start with Ethernet since everyone has that and it's easy to
test. Also, having very clear steps to reproduce would be great.

Thus, I'm going to call it incomplete.

** Changed in: network-manager-applet (Ubuntu)
   Status: Confirmed = Incomplete

** Changed in: policykit (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  Can't unlock UMTS modem with PIN

Status in network-manager-applet package in Ubuntu:
  Incomplete
Status in policykit package in Ubuntu:
  Incomplete

Bug description:
  I can't unlock my UMTS USB modem with Lubuntu 15.04 (It works on
  xubuntu 14.10)

  (nm-applet:3280): nm-applet-WARNING **: Failed to send PIN to devid:
  'c8efb515c36471e33a1e711a672ed5cb45b5c5a2' simid: '(null)' : PolicyKit
  authorization failed: challenge needed for
  'org.freedesktop.ModemManager1.Device.Control'

  lsusb output:
  Bus 003 Device 005: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA 
Modem / E230/E270/E870 HSDPA/HSUPA Modem

  usb-modeswitch usb-modeswitch-data is installed.

  
  Any idea?

  Thank you!

  
  Regards,
Andreas Weller

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager-gnome 0.9.10.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Apr 10 01:06:29 2015
  ExecutablePath: /usr/bin/nm-applet
  InstallationDate: Installed on 2015-03-28 (12 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.141
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
weller 1094f12c6-3f6a-49bc-aff8-ef0ec57f7512  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB1  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/4  
--  ----
 
   eth0 ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1442406/+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 1429531] Re: users-admin cannot create a new user in Lubuntu

2015-04-15 Thread Walter Lapchynski

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

Since the workaround at #1424362 works and the symptoms are similar, I'm
going to call this a dupe.

** This bug has been marked a duplicate of bug 1424362
   permissions issues in LXDE as of Vivid Lubuntu Final Beta

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

Title:
  users-admin cannot create a new user in Lubuntu

Status in gnome-system-tools package in Ubuntu:
  Confirmed

Bug description:
  users-admin cannot create a new user in Lubuntu. Nothing happens when
  I click on '+ Add user'

  I have tried from the menu and after that from a terminal window
  without and with [gk]sudo

  -o-

  It works to add a user with the CLI tool

  sudo adduser newuser

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-system-tools 3.0.0-4ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Mar  8 08:56:58 2015
  InstallationDate: Installed on 2015-03-08 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20150307)
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1429531/+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 1432843] Re: Lubuntu failed to boot

2015-04-14 Thread Walter Lapchynski

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

Confirmed this is a bug in the seed. Julien is on it and it should be
resolved in time for release. This doesn't affect X but I can't remove
that it seems. Alberto? I'm going to dupe this against the other bug and
change the description a bit.

** No longer affects: xorg (Ubuntu)

** Changed in: lubuntu-meta (Ubuntu)
 Assignee: (unassigned) = Julien Lavergne (gilir)

** This bug has been marked a duplicate of bug 1441843
   X server fails to start on post-final Beta Lubuntu Vivid desktop images in 
virtual machines

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1441843] Re: lightdm fails to start on lubuntu desktop images in virtual machines

Calling this high because it makes testing difficult and vivid final is
right around the corner.

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

Title:
  lightdm fails to start on lubuntu desktop images in virtual machines

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  To reproduce boot the lubuntu amd64 image form Arpil 8th in virtaulbox
  4.3.26 the version from the vivid repos.

  I expected virtualbox to start to a working instlal like the
  alterneate does.

  Instead it stopped and X did not start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.18
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.358
  Date: Wed Apr  8 20:13:16 2015
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
  LiveMediaBuild: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150408)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441843/+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 1441843] Re: lightdm fails to start on lubuntu desktop images in virtual machines

Also note that there are no problems on bare metal.

** Changed in: lightdm (Ubuntu)
   Importance: Undecided = High

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

Title:
  lightdm fails to start on lubuntu desktop images in virtual machines

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  To reproduce boot the lubuntu amd64 image form Arpil 8th in virtaulbox
  4.3.26 the version from the vivid repos.

  I expected virtualbox to start to a working instlal like the
  alterneate does.

  Instead it stopped and X did not start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.18
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.358
  Date: Wed Apr  8 20:13:16 2015
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
  LiveMediaBuild: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150408)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441843/+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 1441843] Re: Ubiquity fails to starts on lubuntu desktop images in virtualbox

Confirmed on i386 in VirtualBox 4.3.26 from upstream repos. Was able to
get to the virtual terminal and indeed the system is not frozen but
nothing doing. lightdm fails to start and there seem to be errors
setitng up the display in X.

Not to speak for him but Kamilion mentioned that this also failed with
VMWare Workstation 11.1.

** Summary changed:

- Ubiquity fails to starts on lubuntu desktop images in virtualbox
+ lightdm fails to start on lubuntu desktop images in virtual machines

** Package changed: ubiquity (Ubuntu) = lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
   Importance: High = Undecided

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

Title:
  lightdm fails to start on lubuntu desktop images in virtual machines

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  To reproduce boot the lubuntu amd64 image form Arpil 8th in virtaulbox
  4.3.26 the version from the vivid repos.

  I expected virtualbox to start to a working instlal like the
  alterneate does.

  Instead it stopped and X did not start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.18
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.358
  Date: Wed Apr  8 20:13:16 2015
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
  LiveMediaBuild: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150408)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441843/+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 1441843] Re: lightdm fails to start on lubuntu desktop images in virtual machines

Also note Xubuntu is not affected. Other flavors should be checked.

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

Title:
  lightdm fails to start on lubuntu desktop images in virtual machines

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  To reproduce boot the lubuntu amd64 image form Arpil 8th in virtaulbox
  4.3.26 the version from the vivid repos.

  I expected virtualbox to start to a working instlal like the
  alterneate does.

  Instead it stopped and X did not start.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubiquity 2.21.18
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.358
  Date: Wed Apr  8 20:13:16 2015
  InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
  LiveMediaBuild: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150408)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1441843/+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 1432843] Re: Lubuntu failed to boot

Note here https://bugs.launchpad.net/ubuntu-cdimage/+bug/1441843 that
/usr/lib/xorg/modules/drivers is missing most of its drivers due to the
fact that most, if not all, of the xserver-xorg-video-* packages are
missing. My guess is that this is the problem: they're not in the
manifest! Compare
http://cdimage.ubuntu.com/lubuntu/releases/15.04/beta-1/lubuntu-15.04-beta1
-desktop-amd64.manifest with
http://cdimage.ubuntu.com/lubuntu/releases/15.04/beta-2/lubuntu-15.04-beta2
-desktop-amd64.manifest. Interesting that this works for anyone!

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1432843] Re: Lubuntu failed to boot

You guys that do have this bug should update the bug description so that
it includes the following sections:

STEPS TO REPRODUCE
1.

EXPECTED RESULTS
*

ACTUAL RESULTS
*

AFFECTS
* images
  * Lubuntu amd64/i386 starting 20150316
* hardware
  * 

DOES NOT AFFECT
* images
  * Xubuntu (correct?)
* hardware
  *

Fill in the blanks, of course. Just get rid of what was there before. It
will be archived.

From what we have found on the other bug, it seems that it only affects
Lubuntu (though MATE and Kylin haven't been tested, for example).

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1432843] Re: Lubuntu failed to boot

Can you guys get virtual terminals, out of curiousity? If so, I'd be
interested to see /var/log/syslog and /var/log/Xorg.0.log and
/var/log/lightdm/lightdm.log. Betcha they jive with that other bug.

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1441843] Re: lightdm fails to start on lubuntu desktop images in virtual machines

/var/log/X.org.0.log (http://paste.ubuntu.com/10795553/) shows:

[   109.070] (EE) Device(s) detected, but none match those in the config file.
[   109.070] (EE) 
Fatal server error:
[   109.070] (EE) no screens found(EE) 

/var/log/lightdm/lightdm.log (http://paste.ubuntu.com/10794305/) shows:

[+0.75s] DEBUG: Seat seat0: Creating display server of type x
[+0.75s] DEBUG: Using VT 7
[+0.75s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.75s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.75s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
[+0.75s] DEBUG: DisplayServer x-0: Launching X Server
[+0.76s] DEBUG: Launching process 1504: /usr/bin/X -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.76s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+1.39s] DEBUG: Process 1504 terminated with signal 6
[+1.39s] DEBUG: DisplayServer x-0: X server stopped
[+1.39s] DEBUG: Releasing VT 7
[+1.39s] DEBUG: DisplayServer x-0: Removing X server authority 
/var/run/lightdm/root/:0
[+1.39s] DEBUG: Seat seat0: Display server stopped
[+1.39s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.39s] DEBUG: Seat seat0: Stopping
[+1.39s] DEBUG: Seat seat0: Stopping session
[+1.39s] DEBUG: Seat seat0: Session stopped
[+1.39s] DEBUG: Seat seat0: Stopped
[+1.39s] DEBUG: Required seat has stopped
[+1.39s] DEBUG: Stopping display manager
[+1.39s] DEBUG: Display manager stopped
[+1.39s] DEBUG: Stopping daemon
[+1.40s] DEBUG: Seat seat0: Stopping session
[+1.42s] DEBUG: Exiting with return value 1

/var/log/syslog (http://paste.ubuntu.com/10794321/) shows:

Apr 10 20:13:56 lubuntu systemd[1]: Starting Light Display Manager...
Apr 10 20:13:57 lubuntu systemd[1]: Started Light Display Manager.
Apr 10 20:13:58 lubuntu systemd[1]: lightdm.service: main process exited, 
code=exited, status=1/FAILURE
Apr 10 20:13:58 lubuntu systemd[1]: Unit lightdm.service entered failed state.
Apr 10 20:13:58 lubuntu systemd[1]: lightdm.service failed.
Apr 10 20:13:58 lubuntu systemd[1]: lightdm.service holdoff time over, 
scheduling restart.
Apr 10 20:13:58 lubuntu systemd[1]: start request repeated too quickly for 
lightdm.service
Apr 10 20:13:58 lubuntu systemd[1]: Failed to start Light Display Manager.
Apr 10 20:13:58 lubuntu systemd[1]: Unit lightdm.service entered failed state.
Apr 10 20:13:58 lubuntu systemd[1]: lightdm.service failed.


** Summary changed:

- lightdm fails to start on lubuntu desktop images in virtual machines
+ X server fails to start on lubuntu desktop images in virtual machines

** Package changed: lightdm (Ubuntu) = ubuntu-cdimage

** Summary changed:

- X server fails to start on lubuntu desktop images in virtual machines
+ X server fails to start on post-final Beta Lubuntu Vivid desktop images in 
virtual machines

** Description changed:

- To reproduce boot the lubuntu amd64 image form Arpil 8th in virtaulbox
- 4.3.26 the version from the vivid repos.
+ STEPS TO REPRODUCE
+ 1. Boot daily post-final Beta Lubuntu Vivid desktop image in a virtual machine
+ 2. Select Try Lubuntu without installing or Install Lubuntu from the boot 
menu
  
- I expected virtualbox to start to a working instlal like the alterneate
- does.
+ EXPECTED RESULTS
+ X server starts
  
- Instead it stopped and X did not start.
+ ACTUAL RESULTS
+ X server fails to start
  
- ProblemType: Bug
- DistroRelease: Ubuntu 15.04
- Package: ubiquity 2.21.18
- ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
- Uname: Linux 3.19.0-12-generic x86_64
- ApportVersion: 2.17-0ubuntu1
- Architecture: amd64
- CasperVersion: 1.358
- Date: Wed Apr  8 20:13:16 2015
- InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
- LiveMediaBuild: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150408)
- ProcEnviron:
-  SHELL=/bin/bash
-  TERM=linux
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  XDG_RUNTIME_DIR=set
- SourcePackage: ubiquity
- UpgradeStatus: No upgrade log present (probably fresh install)
+ AFFECTS
+ * virtual machines
+   * VirtualBox 4.3.26, whether upstream or not
+   * VMWare Workstation 11.1
+ * images
+   * Lubuntu Desktop amd64/i386  
+ 
+ DOES NOT AFFECT
+ * images
+   * Xubuntu

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

Title:
  X server fails to start on post-final Beta Lubuntu Vivid desktop
  images in virtual machines

Status in Ubuntu CD image build software:
  Confirmed

Bug description:
  STEPS TO REPRODUCE
  1. Boot daily post-final Beta Lubuntu Vivid desktop image in a virtual machine
  2. Select Try Lubuntu without installing or Install Lubuntu from the boot 
menu

  EXPECTED RESULTS
  X server starts

  ACTUAL RESULTS
  X server fails to start

  AFFECTS
  * virtual machines
* VirtualBox 4.3.26, whether upstream or not

[Desktop-packages] [Bug 1429531] Re: users-admin cannot create a new user in Lubuntu

2015-03-19 Thread Walter Lapchynski

Henk, as on the other bug, it would be useful to know if this works with
the other desktops environments. If so, we should also check against the
older lxsession. Failing that, I'll have to hunt through the manifest
more.

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

Title:
  users-admin cannot create a new user in Lubuntu

Status in gnome-system-tools package in Ubuntu:
  Confirmed

Bug description:
  users-admin cannot create a new user in Lubuntu. Nothing happens when
  I click on '+ Add user'

  I have tried from the menu and after that from a terminal window
  without and with [gk]sudo

  -o-

  It works to add a user with the CLI tool

  sudo adduser newuser

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-system-tools 3.0.0-4ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Mar  8 08:56:58 2015
  InstallationDate: Installed on 2015-03-08 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20150307)
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1429531/+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 1424362] Re: no permissions to install or remove packages in vivid daily lubuntu beta 1

2015-03-18 Thread Walter Lapchynski

Attached is a diff of the manifests of VIvid Alpha 1 and the 20150318
release, grepped carefully for Lubuntu and LXDE components. I think most
of these things are not very suspect. There's no difference in lubuntu-
default-settings. The lubuntu-core and lubuntu-desktop is of no concern
(they're just seeds and anything different in them would show in the
manifest).

I do note there is a different version of lubuntu-software-center, but
as we tested that to not be an issue in other desktop environments,
that's unlikely to be it (for reference here is the diff between the two
versions https://bazaar.launchpad.net/~lubuntu-software-center-team
/lubuntu-software-center/lubuntu-software-center-
trunk/revision/174?remember=167compare_revid=167).

I do notice lxsession has gone through a relatively major change in
version, which is consistent with the big changes it has gone through
lately. That being said, I think it would be wise if we tested the new
version on an Alpha 1 system and see if we can reproduce and/or if we
use the old version on daily.

** Patch added: diff for lubuntu and lxde components in the manifests of vivid 
alpha 1 and 20150318
   
https://bugs.launchpad.net/lubuntu-software-center/+bug/1424362/+attachment/4349394/+files/lubuntu_lxde-vivid-a1_vs_20150318.diff

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

Title:
  no permissions to install or remove packages in vivid daily lubuntu
  beta 1

Status in Lubuntu Software Center:
  Confirmed
Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  Vivid daily version 20150221Lubuntu desktop i386 installed gives following 
message when using Lubuntu Software Center to install a package, whereas 
Synaptic cannot be opened:
  You are not allowed to perform this action
  You don't have the required privileges to perform this action.
  org.freedesktop.PolicyKit.Error.Failed: ('system-bus-name', {'name': 
':1.51'}): org.debian.apt.install-or-remove-packages

  Installing a package using command line works OK.
  Hardware info: https://gist.github.com/2166a864091f84806d39

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-software-center/+bug/1424362/+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 1424362] Re: no permissions to install packages in vivid daily lubuntu beta 2

2015-02-24 Thread Walter Lapchynski

** Changed in: lubuntu-software-center
   Status: New = Confirmed

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

Title:
  no permissions to install packages in vivid daily lubuntu beta 2

Status in Lubuntu Software Center:
  Confirmed
Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  Vivid daily version 20150221Lubuntu desktop i386 installed gives following 
message when using Lubuntu Software Center to install a package, whereas 
Synaptic cannot be opened:
  You are not allowed to perform this action
  You don't have the required privileges to perform this action.
  org.freedesktop.PolicyKit.Error.Failed: ('system-bus-name', {'name': 
':1.51'}): org.debian.apt.install-or-remove-packages

  Installing a package using command line works OK.
  Hardware info: https://gist.github.com/2166a864091f84806d39

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-software-center/+bug/1424362/+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

2015-01-05 Thread Walter Lapchynski

I agree with bronger. Problem solved. Currently using 39.0.2171.65 in a
fresh Lubuntu trusty, which, at this point, is even being used in utopic
and vivid. I'm calling this fixed.

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

** Summary changed:

- chromium 34 from proposed does not take input from keyboard in first entry 
point on several webpages
+ chromium-browser does not accept keyboard input with iBus

-- 
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-browser does not accept keyboard input with iBus

Status in chromium-browser package in Ubuntu:
  Fix Released

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 1034108] Re: Lubuntu, won't take system password, always prompts for keyring

2014-11-26 Thread Walter Lapchynski

This is not fixed because Ubuntu One for cloud storage, etc. is gone:
https://login.ubuntu.com/one-redirect

** Changed in: gnome-keyring (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: lubuntu-meta (Ubuntu)
   Status: New = Invalid

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

Title:
  Lubuntu, won't take system password, always prompts for keyring

Status in “gnome-keyring” package in Ubuntu:
  Invalid
Status in “lubuntu-meta” package in Ubuntu:
  Invalid

Bug description:
  Using Lubuntu 12.04, ubuntu-one is a hassle, because it always prompts for 
this keyring, which isn't intuitive at all since it won't take the keyring 
password.  It should either tell the user it needs the ubuntu-one password, or 
it should load the keyring by default.
  To reproduce, loginto lubuntu when ubuntu-one is installed..

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ubuntuone-client 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  Date: Tue Aug  7 14:22:29 2012
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Alpha amd64 (20120205)
  PackageArchitecture: all
  SourcePackage: ubuntuone-client
  UbuntuOneSyncdaemonExceptionsLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1034108/+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 1273524] Re: LXDE guest session shows error message no session for pid pid for lxsession

2014-11-20 Thread Walter Lapchynski

@kyle-mallory unfortunately no. it got rejected upstream for lacking
information. currently, i'm trying to figure out whether or not lightdm,
lxsession or both are the problem.

what i can tell you so far is someone tried to do it with lxdm and got
the same problem on a regular account. lxdm has its own issues, so i'm
not sure what we can conclude from that, but it sort of suggests the
problem lies with lxsession.

since you have found out about the shell script not being triggered, can
you tell me what's trying to execute it?

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

Title:
  LXDE guest session shows error message no session for pid pid for
  lxsession

Status in One Hundred Papercuts:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lxsession” package in Ubuntu:
  Triaged

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error no session for pid pid for 
lxsession is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1389904] Re: With the recent update to xserver-xorg-video-intel, system boots to a black screen

2014-11-06 Thread Walter Lapchynski

It appears that this affects a very specific chip. That being said, I
can't do much to help diagnose this. With that in mind, it would be
useful to find out exactly what conditions are required for this to
occur. Is it only that particular package? It should be tested across
different OS versions and flavors. Also, what other chips this may apply
to. It's clearly a regression of some kind because it did work, but I
can't push this upstream without adequate information.

** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Incomplete

** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided = High

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

Title:
With the recent update to xserver-xorg-video-intel, system boots to a
black screen

Status in “xserver-xorg-video-intel” package in Ubuntu:
Incomplete

Bug description:
The latest system updates for Lubuntu 14.04 includes an update to the
i915 display driver, which this machine uses.

After applying updates and rebooting, at the end of the boot process,
where normally the login screen appears, the screen remains blank
(with a black background color).

That change has rendered my Lubuntu 14.04 partition completely
unusable, even when booting earlier versions of the kernel.
Regardless the kernel level booted, the system now boots to a blank
screen.

Because of this, I had to report the error on my UbuntuStudio 14.04
partition, to which I have not yet applied updates. So the level of
the Intel i915 driver package in this error report is the version
prior to the updated version that (probably) caused the problem.

1. The release of ubuntu with the problem is Lubuntu 14.04.1, with a
kernel version ending in .39.

2. The last working version of xserver-xorg-video-intel is
2:2.99.910-0ubuntu1 I can't boot by Lubuntu partition anymore to tell
you the version number that fails, but it is later than the indicated
version.

3. Prior to installing system updates, my Lubuntu 14.04.01 system
worked fine, and I was able to boot it and perform my suite of tests
(it's a test system). After applying updates, it boots to a blank
screen, and I cannot do anything with it. I expected the login screen
to appear, but it doesn't, and there is no error message.

4. After applying system updates I expected my system to reboot
normally, allowing me to login. Instead, a blank screen is displayed,
with no error message, and the login screen does not appear after many
minutes of waiting. If I hit the power button, it initiates shutdown.
Hitting several keyboard characters (or typing my password to the
blank screen) had no effect.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-lowlatency 3.13.11.4
Uname: Linux 3.13.0-32-lowlatency i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CurrentDesktop: XFCE
Date: Wed Nov 5 16:13:54 2014
InstallationDate: Installed on 2014-04-28 (191 days ago)
InstallationMedia: Ubuntu-Studio 14.04 LTS Trusty Tahr - Release i386
(20140416.3)
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1389904/+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 1273524] Re: LXDE guest session shows error message no session for pid pid for lxsession

2014-11-05 Thread Walter Lapchynski

thx Brendan. don't see anything too weird. that Source ID line doesn't
appear to be in there. dbus errors. could you `apport  collect`?

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

Title:
  LXDE guest session shows error message no session for pid pid for
  lxsession

Status in One Hundred Papercuts:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lxsession” package in Ubuntu:
  Triaged

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error no session for pid pid for 
lxsession is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1384304] Re: No sound output lubuntu 14.04

2014-11-04 Thread Walter Lapchynski

For one, pulseaudio is not a part of Lubuntu. That shouldn't cause your
problem, but it may complicate things. Also, I would cause this a
support issue. Please check out
https://wiki.ubuntu.com/DebuggingSoundProblems and see if you can't get
to the bottom of this.

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: lubuntu-meta (Ubuntu)

** Changed in: pulseaudio (Ubuntu)
   Status: New = Invalid

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

Title:
  No sound output lubuntu 14.04

Status in “pulseaudio” package in Ubuntu:
  Invalid

Bug description:
  All automatic updates have been installed on my system (bug reporter
  couldn't find an update trail, so that may be an issue, too).

  Recently, in the middle of a session, my sound output ceased. Just
  before it happened I had made minor changes to the Default
  Applications using the GUI - those changes were only to replace
  Abiword and Gnumeric with their Libreoffice equivalents for
  spreadsheets and word processor documents.

  Launching Volume Control settings, the Alsamixer display had no
  indicators for controls listed under 'playback' (f3). Instead, there
  is just an item labelled S/PDIF with '00' in a box above it and this
  does not respond to numeral or arrow keys.

  I have tried reinstalling Pulseaudio. This hasn't helped. I have
  installed pavucontrol. Now, during playback of video and sound files,
  when I view pavucontrol the blue levels indicator for my sound cards
  is moving as if there is a signal, but there is still no sound.  I
  have tried plugging in other speakers to confirm that it's not my
  speakers at fault. I have also tried adjusting the level under the
  'output' tab of pavucontrol, but this has not helped, either.

  Hardware info:

  *-multimedia:0
   description: Audio device
   product: Trinity HDMI Audio Controller
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 1.1
   bus info: pci@:00:01.1
   version: 00
   width: 32 bits
   clock: 33MHz
   capabilities: pm pciexpress msi bus_master cap_list
   configuration: driver=snd_hda_intel latency=0
   resources: irq:50 memory:feb44000-feb47fff
   *-multimedia:1
   description: Audio device
   product: FCH Azalia Controller
   vendor: Advanced Micro Devices, Inc. [AMD]
   physical id: 14.2
   bus info: pci@:00:14.2
   version: 01
   width: 64 bits
   clock: 33MHz
   capabilities: pm bus_master cap_list
   configuration: driver=snd_hda_intel latency=32
   resources: irq:16 memory:feb4-feb43fff

  (NB, I have tried plugging speakers into both devices)

  An unresolved thread on Ubuntuforums.org suggests that one Ubuntu user
  has had this problem on x64 architecture just after intalling version
  3.13.0-37 of the Linux kernel. I have the same Kernel version. Another
  user has had their sound disappear, then reappear after putting their
  laptop in sleepmode overnight. Again, same kernel version, but desktop
  environment unspecified.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lubuntu-desktop 0.55
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 22 16:07:26 2014
  InstallationDate: Installed on 2014-10-04 (18 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: lubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1384304/+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 1273524] Re: lxsession guest session shows error message no session for pid pid for lxsession

2014-11-03 Thread Walter Lapchynski

i installed lightdm 1.8.4-0ubuntu1 from saucy (with lxsession
0.4.9.2-0ubuntu6) and i cannot confirm the bug.

i upgraded lxsession on that same system and i cannot confirm the bug.

long story short, regardless of lxsession version, the bug depends upon
lightdm.

** Summary changed:

- lxsession guest session shows error message no session for pid pid for 
lxsession
+ guest session shows error message no session for pid pid for lxsession

** Also affects: lightdm
   Importance: Undecided
   Status: New

** Changed in: lightdm
   Status: New = Confirmed

** Project changed: lightdm = lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: lightdm (Ubuntu)
   Importance: Undecided = Medium

** Description changed:

  EXPECTED RESULTS:
  Log into guest session with no error messages.
  
  ACTUAL RESULTS:
  Upon log in to guest session, an error no session for pid pid for 
lxsession is printed.
  
  STEPS TO REPRODUCE:
- 1. Using Lubuntu in trusty or utopic with either real or virtual hardware, 
log into guest session.
+ 1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.
  
  AFFECTED VERSIONS:
- 0.4.9.2-0ubuntu7 to 0.4.9.2+git20140410-0ubuntu3
+ lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1

** Summary changed:

- guest session shows error message no session for pid pid for lxsession
+ LXDE guest session shows error message no session for pid pid for 
lxsession

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

Title:
  LXDE guest session shows error message no session for pid pid for
  lxsession

Status in One Hundred Papercuts:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lxsession” package in Ubuntu:
  Triaged

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error no session for pid pid for 
lxsession is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1378423] Re: Virtualbox boots to black screen with daily

2014-10-16 Thread Walter Lapchynski

another successful test:

image:   Xubuntu i386 20141016
vm: VirtualBox 4.3.18-96516~Ubuntu~raring
host:  Kubuntu 14.04

boots straight to the try/install screen without having to flip virtual
terminals or anything.

i'm guessing this is either a host hardware conflict of some kind or
perhaps the issue is related to the amd64 image. no amd64 machine handy
to test right now.

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

Title:
  Virtualbox boots to black screen with daily

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Boot the daily image.

  Get a black screen.

  Go to tty1 - lightdm has started - running sudo service lightdm status
  echoes start/waiting

  Return to tty7 and the login dialogue has now appeared

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.344
  Date: Tue Oct  7 15:53:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1378423/+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 1216788] Re: #!/usr/bin/python files and similar variants are not shown as executable files

** Changed in: lxde-icon-theme (Ubuntu)
   Status: New = Incomplete

** Changed in: shared-mime-info (Ubuntu)
   Status: New = Incomplete

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

Title:
  #!/usr/bin/python files and similar variants are not shown as
  executable files

Status in “lxde-icon-theme” package in Ubuntu:
  Incomplete
Status in “shared-mime-info” package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 13.10 dev with shared-mime-info 1.1-0ubuntu4. For a few days 
after upgrading the system I have noticed that python-files aren't shown as 
executable files anymore. I have already opened a bug report on upstream for 
this: https://bugs.freedesktop.org/show_bug.cgi?id=68494
  But I'm not sure if this is really a bug in shared-mime-info because after 
downgrading shared-mime-info, PCManFM and libfm to the versions from Ubuntu 
13.04 (libfm-data, libfm-gtk-bin, libfm-gtk-data, libfm-gtk3, libfm3, pcmanfm, 
shared-mime-info) and rebooting the system the problem still exists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxde-icon-theme/+bug/1216788/+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 1216788] Re: #!/usr/bin/python files and similar variants are not shown as executable files

based on what you have shown, it's unclear what the issue is:
1. are the files executable in the terminal? if so, you should check the 
executable flags. this may be obvious, but it's worth looking into.
2. are they only files that use #!/usr/bin/python? what about python3? what 
about #!/usr/bin/env python? for that matter, where does /usr/bin/python point 
to? it is a symbolic link after all.
3. is it only a problem being able to double click them in the GUI? if so, try 
running pcmanfm in the terminal and double  clicking on the icon. what output 
do you get in the terminal?

furthermore, what are the versions of everything are we talking about?
what 14.10 image? a release or a daily image? which one? what is the
last version you can say this was working with?

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

Title:
  #!/usr/bin/python files and similar variants are not shown as
  executable files

Status in “lxde-icon-theme” package in Ubuntu:
  Incomplete
Status in “shared-mime-info” package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 13.10 dev with shared-mime-info 1.1-0ubuntu4. For a few days 
after upgrading the system I have noticed that python-files aren't shown as 
executable files anymore. I have already opened a bug report on upstream for 
this: https://bugs.freedesktop.org/show_bug.cgi?id=68494
  But I'm not sure if this is really a bug in shared-mime-info because after 
downgrading shared-mime-info, PCManFM and libfm to the versions from Ubuntu 
13.04 (libfm-data, libfm-gtk-bin, libfm-gtk-data, libfm-gtk3, libfm3, pcmanfm, 
shared-mime-info) and rebooting the system the problem still exists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxde-icon-theme/+bug/1216788/+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 1216788] Re: Files previously shown with a gear icon (like #!/usr/bin/python) are now shown as text files

if you double click on the file, does it open like normal?

are there ANY executable files that show the icon?

where's the upstream link to this hint you got?

what version of 14.10? is it an alpha? beta? daily image?

what versions did this last work with?

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

Title:
  Files previously shown with a gear icon (like #!/usr/bin/python) are
  now shown as text files

Status in “lxde-icon-theme” package in Ubuntu:
  New
Status in “shared-mime-info” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 13.10 dev with shared-mime-info 1.1-0ubuntu4. For a few days 
after upgrading the system I have noticed that python-files aren't shown as 
executable files anymore. I have already opened a bug report on upstream for 
this: https://bugs.freedesktop.org/show_bug.cgi?id=68494
  But I'm not sure if this is really a bug in shared-mime-info because after 
downgrading shared-mime-info, PCManFM and libfm to the versions from Ubuntu 
13.04 (libfm-data, libfm-gtk-bin, libfm-gtk-data, libfm-gtk3, libfm3, pcmanfm, 
shared-mime-info) and rebooting the system the problem still exists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxde-icon-theme/+bug/1216788/+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 1378423] Re: Virtualbox boots to black screen with daily

using lubuntu desktop i386 20141014, i have no problems. don't have an
amd64 machine handy at present.

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

Title:
  Virtualbox boots to black screen with daily

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Boot the daily image.

  Get a black screen.

  Go to tty1 - lightdm has started - running sudo service lightdm status
  echoes start/waiting

  Return to tty7 and the login dialogue has now appeared

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.344
  Date: Tue Oct  7 15:53:54 2014
  LiveMediaBuild: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1378423/+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 1216788] Re: Files previously shown with a gear icon (like #!/usr/bin/python) are now shown as text files

If you don't have lxde-icon-theme, do you still have the problem?

** Changed in: shared-mime-info (Ubuntu)
   Status: New = Invalid

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

Title:
  Files previously shown with a gear icon (like #!/usr/bin/python) are
  now shown as text files

Status in “lxde-icon-theme” package in Ubuntu:
  Confirmed
Status in “shared-mime-info” package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 13.10 dev with shared-mime-info 1.1-0ubuntu4. For a few days 
after upgrading the system I have noticed that python-files aren't shown as 
executable files anymore. I have already opened a bug report on upstream for 
this: https://bugs.freedesktop.org/show_bug.cgi?id=68494
  But I'm not sure if this is really a bug in shared-mime-info because after 
downgrading shared-mime-info, PCManFM and libfm to the versions from Ubuntu 
13.04 (libfm-data, libfm-gtk-bin, libfm-gtk-data, libfm-gtk3, libfm3, pcmanfm, 
shared-mime-info) and rebooting the system the problem still exists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxde-icon-theme/+bug/1216788/+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 1216788] Re: #!/usr/bin/python files and similar variants are not shown as executable files

2014-10-13 Thread Walter Lapchynski

13.10 is EOL. please test with a current version. you can see
supported releases, end of life dates, etc. here:
https://wiki.ubuntu.com/Releases

On 10/13/14, Sworddragon 1216...@bugs.launchpad.net wrote:
 ** Also affects: lxde-icon-theme (Ubuntu)
Importance: Undecided
Status: New

 --
 You received this bug notification because you are a member of Lubuntu
 Packages Team, which is subscribed to lxde-icon-theme in Ubuntu.
 https://bugs.launchpad.net/bugs/1216788

 Title:
   #!/usr/bin/python files and similar variants are not shown as
   executable files

 Status in “lxde-icon-theme” package in Ubuntu:
   New
 Status in “shared-mime-info” package in Ubuntu:
   New

 Bug description:
   I'm using Ubuntu 13.10 dev with shared-mime-info 1.1-0ubuntu4. For a few
 days after upgrading the system I have noticed that python-files aren't
 shown as executable files anymore. I have already opened a bug report on
 upstream for this: https://bugs.freedesktop.org/show_bug.cgi?id=68494
   But I'm not sure if this is really a bug in shared-mime-info because after
 downgrading shared-mime-info, PCManFM and libfm to the versions from Ubuntu
 13.04 (libfm-data, libfm-gtk-bin, libfm-gtk-data, libfm-gtk3, libfm3,
 pcmanfm, shared-mime-info) and rebooting the system the problem still
 exists.

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/lxde-icon-theme/+bug/1216788/+subscriptions



** Bug watch added: freedesktop.org Bugzilla #68494
   https://bugs.freedesktop.org/show_bug.cgi?id=68494

** Changed in: lxde-icon-theme (Ubuntu)
   Status: New = Invalid

** Changed in: shared-mime-info (Ubuntu)
   Status: New = Invalid

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

Title:
  #!/usr/bin/python files and similar variants are not shown as
  executable files

Status in “lxde-icon-theme” package in Ubuntu:
  Invalid
Status in “shared-mime-info” package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 13.10 dev with shared-mime-info 1.1-0ubuntu4. For a few days 
after upgrading the system I have noticed that python-files aren't shown as 
executable files anymore. I have already opened a bug report on upstream for 
this: https://bugs.freedesktop.org/show_bug.cgi?id=68494
  But I'm not sure if this is really a bug in shared-mime-info because after 
downgrading shared-mime-info, PCManFM and libfm to the versions from Ubuntu 
13.04 (libfm-data, libfm-gtk-bin, libfm-gtk-data, libfm-gtk3, libfm3, pcmanfm, 
shared-mime-info) and rebooting the system the problem still exists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxde-icon-theme/+bug/1216788/+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 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-23 Thread Walter Lapchynski

does this work ok on real installs?

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

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-23 Thread Walter Lapchynski

Does 1.1.8 work on real hardware?

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

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1246119] Re: printing some pdfs results in undefinedresult error due to awidthshow command on HP 4050

2013-10-30 Thread Walter Lapchynski

I should point out that unfiltered (lp -d queue-name -oraw file) works 
fine, too.


** Attachment added: var.log.cups.error_log
   
https://bugs.launchpad.net/bugs/1246119/+attachment/3895928/+files/var.log.cups.error_log

** Attachment added: var.spool.cups.d00399-001
   
https://bugs.launchpad.net/bugs/1246119/+attachment/3895929/+files/var.spool.cups.d00399-001

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

Title:
  printing some pdfs results in undefinedresult error due to
  awidthshow command on HP 4050

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  thought i had an okular/poppler error so originally reported on kde's
  bug tracker (https://bugs.kde.org/show_bug.cgi?id=321046) but in the
  end, the file converts to ps and displays on ghostscript just fine.

  the other commenter with similar symptoms also has an hp 4050 so i'm
  inclined to believe the problem lies here somewhere.

  though i believe that there is something different between the old and
  new versions, i find nothing really different with the ppds (except
  for some carriage returns), so perhaps it's an issue with cups more
  generally?

  if that's the case, i'm somewhat confused because i can print to
  another printer without problems. maybe a newer version of cups has
  deprecated one of the definitions in the ppd?

  i'm also confused about the fact that the awidthshow command is not to
  be found in the ps or the ppd.

  i'm happy to do any troubleshooting necessary, but i'm unclear on what
  to do.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cups 1.6.2-1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  Date: Tue Oct 29 15:21:17 2013
  InstallationDate: Installed on 2013-05-14 (167 days ago)
  InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  KernLog:
   
  Lpstat:
   device for sales: smb://SALES/BFDATA1/BF1-salesprinter
   device for xerox: socket://192.168.1.5:9100
  MachineType: Hewlett-Packard HP Compaq dc7800 Small Form Factor
  MarkForUpload: True
  Papersize: letter
  PpdFiles:
   sales: HP LaserJet 4050 Series Postscript (recommended)
   xerox: Xerox ColorQube 9303
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic 
root=UUID=cdcd85f2-36ad-4218-9e34-7e8f8994fd26 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.04
  dmi.board.asset.tag: 2UA813065T
  dmi.board.name: 0AA8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA813065T
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800SmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq dc7800 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard

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

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

Re: [Desktop-packages] [Bug 1246119] Re: printing some pdfs results in undefinedresult error due to awidthshow command on HP 4050

2013-10-30 Thread Walter Lapchynski

On 10/30/2013 02:02 PM, Roland Brand wrote:
 Please let me know, if I can help in tracking down the problem.

If i were you, i'd follow Till's advice above. The sections you need to 
follow are:
https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log
https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data

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

Title:
  printing some pdfs results in undefinedresult error due to
  awidthshow command on HP 4050

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  thought i had an okular/poppler error so originally reported on kde's
  bug tracker (https://bugs.kde.org/show_bug.cgi?id=321046) but in the
  end, the file converts to ps and displays on ghostscript just fine.

  the other commenter with similar symptoms also has an hp 4050 so i'm
  inclined to believe the problem lies here somewhere.

  though i believe that there is something different between the old and
  new versions, i find nothing really different with the ppds (except
  for some carriage returns), so perhaps it's an issue with cups more
  generally?

  if that's the case, i'm somewhat confused because i can print to
  another printer without problems. maybe a newer version of cups has
  deprecated one of the definitions in the ppd?

  i'm also confused about the fact that the awidthshow command is not to
  be found in the ps or the ppd.

  i'm happy to do any troubleshooting necessary, but i'm unclear on what
  to do.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cups 1.6.2-1ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic i686
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  Date: Tue Oct 29 15:21:17 2013
  InstallationDate: Installed on 2013-05-14 (167 days ago)
  InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  KernLog:
   
  Lpstat:
   device for sales: smb://SALES/BFDATA1/BF1-salesprinter
   device for xerox: socket://192.168.1.5:9100
  MachineType: Hewlett-Packard HP Compaq dc7800 Small Form Factor
  MarkForUpload: True
  Papersize: letter
  PpdFiles:
   sales: HP LaserJet 4050 Series Postscript (recommended)
   xerox: Xerox ColorQube 9303
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic 
root=UUID=cdcd85f2-36ad-4218-9e34-7e8f8994fd26 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.04
  dmi.board.asset.tag: 2UA813065T
  dmi.board.name: 0AA8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA813065T
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800SmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq dc7800 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1246119/+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 827316] Re: DuckDuckGo should be added to the search engine ballot

2012-10-08 Thread Walter Lapchynski

True with the latest in Quantal, too.

chromium-browser:
  Installed: 20.0.1132.47~r144678-0ubuntu6
  Candidate: 20.0.1132.47~r144678-0ubuntu6
  Version table:
 *** 20.0.1132.47~r144678-0ubuntu6 0
500 http://us.archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
100 /var/lib/dpkg/status

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

Title:
  DuckDuckGo should be added to the search engine ballot

Status in Chromium Browser:
  Unknown
Status in “chromium-browser” package in Ubuntu:
  Triaged

Bug description:
  When the Chromium browser is started in Lubuntu for the first time, a
  query is made to choose the default search engine.  The search engine
  duckduckgo.com is missing from the list of choices.  Please add it.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: chromium-browser 12.0.742.112~r90304-0ubuntu0.11.04.1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  ChromiumPrefs:
   browser/check_default_browser = **unset** (no such key yet)
   extensions/settings =
(no entry found in the Preferences file)
  Date: Tue Aug 16 15:23:44 2011
  Desktop-Session:
   DESKTOP_SESSION = Lubuntu
   XDG_CONFIG_DIRS = /etc/xdg/lubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/etc/xdg/lubuntu:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg
  DetectedPlugins: (no entry found in the Preferences file)
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Lubuntu 11.04 Natty Narwhal - i386 (20101203)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/827316/+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 1060452] Re: alsamixer fails to load on quantal ppc

** Summary changed:

- no alsamixer, quantal, powerpc
+ alsamixer fails to load on quantal ppc

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

Title:
  alsamixer fails to load on quantal ppc

Status in “alsa-utils” package in Ubuntu:
  Confirmed

Bug description:
  System G4 iBook 
  1.42GHz CPU, 1.5GHz RAM. 
  Lubuntu Quantal daily build October 1. 
  Fresh install

  When initially lauched alsamixer in terminal it showed as file or
  directory does not exist.  I reinstalled asla-utils package and ran
  rm /etc/modprobe.d/blacklist.local.conf, which fixed the problem in
  12.04.  This time it did not; alsamixer shows in terminal, but with
  the message this sound device does not have any controls,  no sound
  in system, or loudspeaker icon in taskbar.

  Is this a bug or faulty config?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-utils 1.0.25-3ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Tue Oct  2 22:43:19 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1060452/+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 1060452] Re: alsamixer fails to load on quantal ppc

same here, different ppc. the relevant error, even without the -a switch is:
cannot open mixer: No such file or directory 

i tried to use the debugging option of -a and initially got an error
trying to find /usr/lib/powerpc-linux-gnu/alsa-lib/smixer/smixer-
python.so so i installed libasound2-python and then got an error trying
to find /usr/lib/powerpc-linux-gnu/alsa-lib/smixer/python/main.py

in the process of reporting this, i got on my not-quite-so-updated
precise x86 and tried alsamixer -a and got the same error with i386
instead of powerpc. however, alsamixer alone ran fine.

so i'm thinking that there's a problem with the -a switch that may exist
even in previous versions and i'm also thinking that something is amiss
with alsamixer on this version. don't have a quantal x86 install to
compare to presently.

it is also curious to note that lubuntu-core installs alsa-utils which
installs libasound2 which suggests libasound2-python. if this is
required for some reason, why is it only suggested?

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

Title:
  alsamixer fails to load on quantal ppc

Status in “alsa-utils” package in Ubuntu:
  Confirmed

Bug description:
  System G4 iBook 
  1.42GHz CPU, 1.5GHz RAM. 
  Lubuntu Quantal daily build October 1. 
  Fresh install

  When initially lauched alsamixer in terminal it showed as file or
  directory does not exist.  I reinstalled asla-utils package and ran
  rm /etc/modprobe.d/blacklist.local.conf, which fixed the problem in
  12.04.  This time it did not; alsamixer shows in terminal, but with
  the message this sound device does not have any controls,  no sound
  in system, or loudspeaker icon in taskbar.

  Is this a bug or faulty config?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-utils 1.0.25-3ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Tue Oct  2 22:43:19 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1060452/+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 1061790] Re: misbehaving X on quantal ppc w/ nvidia geforce fx go5200

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

Title:
  misbehaving X on quantal ppc w/ nvidia geforce fx go5200

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  i put a lot of information here before it was suggested to make a new bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518

  but to summarize the only way i could get X to start was by turning of KMS, 
e.g. nomodeset or nouveau.modeset=0 boot parameters. when i did, i got such 
horrible graphics i wasn't able to even complete the install. a picture can be 
found here:
  http://imgur.com/ArhrV
  even using an alternate to directly do the install, the result was plagued 
with the same problems.

  so i set to make an xorg.conf. by auto-configuring the file per instructions 
here:
  https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_configure_an_xorg.conf_file.3F
  and turning off 3d acceleration which was suggested here:
  http://ubuntuforums.org/showthread.php?t=2066064

  i tried several other things, like disabling other outputs and adding 
modelines, but this was deemed unnecessarily so i whittled the xorg.conf down 
to the minimum which you can find along with dmesg and Xorg.0.log here:
  http://paste.ubuntu.com/1260328/

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Thu Oct  4 10:58:10 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
   TERM=screen
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1061790/+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 1061790] [NEW] misbehaving X on quantal ppc w/ nvidia geforce fx go5200

Public bug reported:

i put a lot of information here before it was suggested to make a new bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518

but to summarize the only way i could get X to start was by turning of KMS, 
e.g. nomodeset or nouveau.modeset=0 boot parameters. when i did, i got such 
horrible graphics i wasn't able to even complete the install. a picture can be 
found here:
http://imgur.com/ArhrV
even using an alternate to directly do the install, the result was plagued with 
the same problems.

so i set to make an xorg.conf. by auto-configuring the file per instructions 
here:
https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_configure_an_xorg.conf_file.3F
and turning off 3d acceleration which was suggested here:
http://ubuntuforums.org/showthread.php?t=2066064

i tried several other things, like disabling other outputs and adding 
modelines, but this was deemed unnecessarily so i whittled the xorg.conf down 
to the minimum which you can find along with dmesg and Xorg.0.log here:
http://paste.ubuntu.com/1260328/

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
Uname: Linux 3.5.0-16-powerpc-smp ppc
ApportVersion: 2.6.1-0ubuntu1
Architecture: powerpc
Date: Thu Oct  4 10:58:10 2012
InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
ProcEnviron:
 TERM=screen
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug nouveau nvidia powerpc quantal xorg.conf

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

Title:
  misbehaving X on quantal ppc w/ nvidia geforce fx go5200

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  i put a lot of information here before it was suggested to make a new bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518

  but to summarize the only way i could get X to start was by turning of KMS, 
e.g. nomodeset or nouveau.modeset=0 boot parameters. when i did, i got such 
horrible graphics i wasn't able to even complete the install. a picture can be 
found here:
  http://imgur.com/ArhrV
  even using an alternate to directly do the install, the result was plagued 
with the same problems.

  so i set to make an xorg.conf. by auto-configuring the file per instructions 
here:
  https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_configure_an_xorg.conf_file.3F
  and turning off 3d acceleration which was suggested here:
  http://ubuntuforums.org/showthread.php?t=2066064

  i tried several other things, like disabling other outputs and adding 
modelines, but this was deemed unnecessarily so i whittled the xorg.conf down 
to the minimum which you can find along with dmesg and Xorg.0.log here:
  http://paste.ubuntu.com/1260328/

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Thu Oct  4 10:58:10 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
   TERM=screen
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1061790/+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 1061790] Re: misbehaving X on quantal ppc w/ nvidia geforce fx go5200

** Description changed:

  i put a lot of information here before it was suggested to make a new bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518
  
  but to summarize the only way i could get X to start was by turning of KMS, 
e.g. nomodeset or nouveau.modeset=0 boot parameters. when i did, i got such 
horrible graphics i wasn't able to even complete the install. a picture can be 
found here:
  http://imgur.com/ArhrV
  even using an alternate to directly do the install, the result was plagued 
with the same problems.
  
  so i set to make an xorg.conf. by auto-configuring the file per instructions 
here:
  https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_configure_an_xorg.conf_file.3F
  and turning off 3d acceleration which was suggested here:
  http://ubuntuforums.org/showthread.php?t=2066064
+ and found success.
  
  i tried several other things, like disabling other outputs and adding 
modelines, but this was deemed unnecessarily so i whittled the xorg.conf down 
to the minimum which you can find along with dmesg and Xorg.0.log here:
  http://paste.ubuntu.com/1260328/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Thu Oct  4 10:58:10 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
-  TERM=screen
-  SHELL=/bin/bash
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  LANGUAGE=en_US:en
+  TERM=screen
+  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  LANGUAGE=en_US:en
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  misbehaving X on quantal ppc w/ nvidia geforce fx go5200

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  i put a lot of information here before it was suggested to make a new bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518

  but to summarize the only way i could get X to start was by turning of KMS, 
e.g. nomodeset or nouveau.modeset=0 boot parameters. when i did, i got such 
horrible graphics i wasn't able to even complete the install. a picture can be 
found here:
  http://imgur.com/ArhrV
  even using an alternate to directly do the install, the result was plagued 
with the same problems.

  so i set to make an xorg.conf. by auto-configuring the file per instructions 
here:
  https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_configure_an_xorg.conf_file.3F
  and turning off 3d acceleration which was suggested here:
  http://ubuntuforums.org/showthread.php?t=2066064
  and found success.

  i tried several other things, like disabling other outputs and adding 
modelines, but this was deemed unnecessarily so i whittled the xorg.conf down 
to the minimum which you can find along with dmesg and Xorg.0.log here:
  http://paste.ubuntu.com/1260328/

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Thu Oct  4 10:58:10 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
   TERM=screen
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1061790/+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 1061790] Re: misbehaving X on quantal ppc w/ nvidia geforce fx go5200

good point. you can see dmesg/Xorg.0.log for the default boot here:
http://paste.ubuntu.com/1254953/
and indeed No devices detected is at the bottom

if it's relevant to anyone curious, here's the same info for nomodeset:
http://paste.ubuntu.com/1255047/

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

Title:
  misbehaving X on quantal ppc w/ nvidia geforce fx go5200

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  i put a lot of information here before it was suggested to make a new bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1043518

  but to summarize the only way i could get X to start was by turning of KMS, 
e.g. nomodeset or nouveau.modeset=0 boot parameters. when i did, i got such 
horrible graphics i wasn't able to even complete the install. a picture can be 
found here:
  http://imgur.com/ArhrV
  even using an alternate to directly do the install, the result was plagued 
with the same problems.

  so i set to make an xorg.conf. by auto-configuring the file per instructions 
here:
  https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_configure_an_xorg.conf_file.3F
  and turning off 3d acceleration which was suggested here:
  http://ubuntuforums.org/showthread.php?t=2066064
  and found success.

  i tried several other things, like disabling other outputs and adding 
modelines, but this was deemed unnecessarily so i whittled the xorg.conf down 
to the minimum which you can find along with dmesg and Xorg.0.log here:
  http://paste.ubuntu.com/1260328/

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Thu Oct  4 10:58:10 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
   TERM=screen
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1061790/+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 1060452] Re: alsamixer fails to load on quantal ppc

no luck having sound with the latest liveCD so i'm wondering if this
really isn't a more low-level problem.

i tried grepping dmesg and no luck. i do get something out of syslog:

$ cat /var/log/syslog |grep -ie audio -ie sound
Oct  4 14:31:57 amorphous pbbuttonsd: INFO: Soundsystem requested: ALSA and at 
least activated: none.
Oct  4 14:33:25 amorphous pbbuttonsd: INFO: Soundsystem requested: ALSA and at 
least activated: none.
Oct  4 14:36:08 amorphous pbbuttonsd: INFO: Soundsystem requested: ALSA and at 
least activated: none.
Oct  4 16:35:20 amorphous pbbuttonsd: INFO: Soundsystem requested: ALSA and at 
least activated: none.

but i don't think that's particularly helpful.

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

Title:
  alsamixer fails to load on quantal ppc

Status in “alsa-utils” package in Ubuntu:
  Confirmed

Bug description:
  System G4 iBook 
  1.42GHz CPU, 1.5GHz RAM. 
  Lubuntu Quantal daily build October 1. 
  Fresh install

  When initially lauched alsamixer in terminal it showed as file or
  directory does not exist.  I reinstalled asla-utils package and ran
  rm /etc/modprobe.d/blacklist.local.conf, which fixed the problem in
  12.04.  This time it did not; alsamixer shows in terminal, but with
  the message this sound device does not have any controls,  no sound
  in system, or loudspeaker icon in taskbar.

  Is this a bug or faulty config?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-utils 1.0.25-3ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.25-powerpc-smp 3.5.4
  Uname: Linux 3.5.0-16-powerpc-smp ppc
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: powerpc
  Date: Tue Oct  2 22:43:19 2012
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta powerpc (20121001)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1060452/+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 1060452] Re: alsamixer fails to load on quantal ppc