[Bug 2029480] Re: SyntaxWarnings with Python3.12

2024-09-04 Thread Till Kamppeter
Done. Synced BleachBit 4.6.0-4 right now, thanks for investigating.

** Changed in: bleachbit (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  SyntaxWarnings with Python3.12

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2029480] Re: SyntaxWarnings with Python3.12

2024-09-03 Thread Till Kamppeter
** Also affects: rhythmbox (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  SyntaxWarnings with Python3.12

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055346] Re: Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble

2024-02-28 Thread Till Kamppeter
** Patch added: "ipp-usb_0.9.23-1build1_0.9.24-0ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ipp-usb/+bug/2055346/+attachment/5750424/+files/ipp-usb_0.9.23-1build1_0.9.24-0ubuntu1.debdiff

** Also affects: golang-github-openprinting-goipp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: golang-github-openprinting-goipp (Ubuntu)
   Importance: Undecided => High

** Changed in: golang-github-openprinting-goipp (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to golang-github-openprinting-goipp in
Ubuntu.
https://bugs.launchpad.net/bugs/2055346

Title:
  Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-openprinting-goipp/+bug/2055346/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055346] [NEW] Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble

2024-02-28 Thread Till Kamppeter
Public bug reported:

These packages are for IPP-over-USB and they contain not only bug fixes
but also several quirk workarounds to especially make printers from
Pantum but also devices of other manufacturers working.

Unfortunately, goipp is not in my PPU list (I do not know whether ipp-
usb is there).

** Affects: golang-github-openprinting-goipp (Ubuntu)
 Importance: High
 Assignee: Thomas Ward (teward)
 Status: New

** Affects: ipp-usb (Ubuntu)
 Importance: High
 Assignee: Thomas Ward (teward)
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ipp-usb in Ubuntu.
https://bugs.launchpad.net/bugs/2055346

Title:
  Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-openprinting-goipp/+bug/2055346/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1972856] Re: Cannot add printer

2022-05-10 Thread Till Kamppeter
Could you run the command

driverless

and post the output here?

Does it contain the printer's URI
ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/
or ipps://HPF80DAC5CDC21.local:631/ipp/print ?

could you also run

driverless 
'ipps://HP%20OfficeJet%20Pro%208020%20series%20%5B5CDC21%5D._ipps._tcp.local/' 
> 1.ppd
driverless 'ipps://HPF80DAC5CDC21.local:631/ipp/print' > 2.ppd

and attach the files 1.ppd and 2.ppd? Please do not compress them and do
not package them together, attach them one by one. Thanks.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  Cannot add printer

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1971473] Re: Untranslated desktop file

2022-05-03 Thread Till Kamppeter
The "Printers" part of the GNOME Control Center is not system-config-
printer, moving ...

** Package changed: system-config-printer (Ubuntu) => gnome-control-
center (Ubuntu)

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

Title:
  Untranslated desktop file

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1964545] Re: 42beta: moving mouse as screen is fading to screensaver prevents input to shell

2022-03-25 Thread Till Kamppeter
If this situation occurs for me and I press ALT + TAB then, I get back
to normal and can use mouse and keyboard as usual again.

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

Title:
  42beta: moving mouse as screen is fading to screensaver prevents input
  to shell

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


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1891157] Re: [MIR] ipp-usb

2020-08-19 Thread Till Kamppeter
I have talked with the upstream maintainer of ipp-usb, Alexander Pevzner
now and he will emove the dependency on ini.v1.

** Changed in: golang-github-openprinting-goipp (Ubuntu)
   Status: Incomplete => New

** Changed in: golang-gopkg-ini.v1 (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to golang-github-openprinting-goipp in
Ubuntu.
https://bugs.launchpad.net/bugs/1891157

Title:
  [MIR] ipp-usb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-openprinting-goipp/+bug/1891157/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1738442] Re: When installing a printer, the process gets stuck at "Loading drivers database..."

2020-05-19 Thread Till Kamppeter
*** This bug is a duplicate of bug 1872564 ***
https://bugs.launchpad.net/bugs/1872564

** This bug is no longer a duplicate of bug 1721704
   Printer settings stuck on loading drivers database
** This bug has been marked a duplicate of bug 1872564
   /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

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

Title:
  When installing a printer, the process gets stuck at "Loading drivers
  database..."

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1871913] Re: super key does not work with secondary keyboard layout

2020-04-14 Thread Till Kamppeter
I have found out now that for me the problem occurs only if "Pointer
Location" on the "Keyboard & Mouse" page of the gnome-tweaks utility is
set. I have turned it off now and the left Ctrl key now works with all
keyboard layouts again.

If you happen to not find the mouse pointer sometimes, simply make it
bigger, with "Cursor Size" under "Universal Access" in the GNOME Control
Center.

See also

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2603

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

Title:
  super key does not work with secondary keyboard layout

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1872230] Re: With any US international layout left Ctrl key does not work

2020-04-14 Thread Till Kamppeter
UPDATE: For me the problem occurs only if "Pointer Location" on the
"Keyboard & Mouse" page of the gnome-tweaks utility is set. I have
turned it off now and the left Ctrl key now works with all keyboard
layouts again.

If you happen to not find the mouse pointer sometimes, simply make it
bigger, with "Cursor Size" under "Universal Access" in the GNOME Control
Center.

Daniel, thanks for your investigations and the link to the issue report
on GNOME's GitLab, where I have found the hint with the "Pointer
Location".

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

Title:
  With any US international layout left Ctrl key does not work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1872230] [NEW] With any US international layout left Ctrl key does not work

2020-04-11 Thread Till Kamppeter
Public bug reported:

I am using 20.04 Focal.

I am using a US international keyboard layout with dead keys, so that I
can enter text in many different languages. After I had rebooted my
system today and so loaded the newest GNOME Shell, the left Ctrl key
stopped working in the terminal windows and also in emacs, while the
right Ctrl still works. To get the left Ctrl working again I have to
switch to a plain US English keyboard layout, without dead keys.

I have also tried the different alternatives of US International
keyboard layouts, each of them seems to work as intended but the left
Ctrl key is not working. Only with plain US English layout I get the
left Ctrl working.

** Affects: gnome-shell (Ubuntu)
 Importance: Critical
 Status: New

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

Title:
  With any US international layout left Ctrl key does not work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1855615] Re: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

2019-12-10 Thread Till Kamppeter
To turn off color management on a CUPS print job you have to turn on
calibration mode. On the command line it is done as follows:

lp -d printer -o cm-calibration=1 file

The option has the possible values 0 and 1.

The button mentioned should probably add this option to the print job,
or when it is not in the context of printing a job but managing a print
queue it should set the default of this option on the print queue. The
option is available for all printers (provided by cups-filters).

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

Title:
  Device colour profiles - on / off button not working Ubuntu 18.04.3LTS

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2019-06-05 Thread Till Kamppeter
Closing Cosmic task as Cosmic goes EOL in a month from now and Disco is
available. In addition, the problem only occurs when updating from an
older Ubuntu release. So it is recommended to generally update to Disco
instead of to Cosmic and in case one updated to Cosmic getting this
problem to update again to Disco.


** Changed in: gtk+3.0 (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread Till Kamppeter
Thanks, nice collection of crashes, but no NetworkManager.

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-03-26 Thread Till Kamppeter
To anyone who has observed this problem:

Please check the contents of your /var/crash/ directory.

Is there a file with the ".crash" extension and NetworkManager or
networkmanager in its name and the day when you observed the problem as
file date?

In this case also NetworkManager has crashed.

Then please call "apport-bug" with this file as command line argument:

apport-bug /var/crash/...

This will generate a new bug report with more info about your crash of
NetworkManager. Add a link to this bug report here.

Or tell here for the case that you do not get a crash file related to
NetworkManager.


** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-03-22 Thread Till Kamppeter
This temporary queue (Kyocera_ECOSYS_P6026cdn) is actually not needed
here. Therefore I have reported this upstream issue on CUPS:

https://github.com/apple/cups/issues/5546

But anyhow, the GUIs need to correctly support temporary print queues of
CUPS.

** Bug watch added: github.com/apple/cups/issues #5546
   https://github.com/apple/cups/issues/5546

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

Title:
  "driverless" printer workflow has bad usability/ is partly broken

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-03-20 Thread Till Kamppeter
I think the problem here is CUPS' own method of generating temporary
queues for discovered driverless printers. gnome-control-center, and
probably other GUIs, like the GTK print dialog, cannot cope with this.
So we leave this bug report assigned to gnome-control-center for now.

Christian, if you stop cups-browsed you have still auto-generated print
queues. This is because CUPS itself kicks in here.

If you run

lpstat -e

you see queue names which you do not see with

lpstat -v

The extra queue names are temporary CUPS queues. These are created by
CUPS if you try to print on them or to access them in general, and they
are removed by CUPS again after 1 minute of inactivity.

gnome-control-center probably gets completely confused by that. It can
have seen such a queue as actual queue, shortly after such a queue was
used, and added it to its list. Now, more than a minute later, the user
clicks on the entry, the queue is not there any more, and he gets
something unexpected, an error message, an empty option dialog, a
"(null):631".

gnome-control-center and all other printing GUIs need to be adapted to
CUPS' temporary print queues.

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

Title:
  "driverless" printer workflow has bad usability/ is partly broken

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-03-20 Thread Till Kamppeter
Christian, both your attached PPD files are auto-generated, and both
pass cupstestppd.

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

Title:
  "driverless" printer workflow has bad usability/ is partly broken

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-03-20 Thread Till Kamppeter
Christian, first, it seems that you did "cupstestppd" on a PPD file
which is not auto-generated:

--
$ sudo cupstestppd /etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd
/etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd: FAIL
  **FAIL** Missing choice *Option18 SDCard in UIConstraints "*KCCollate 
CustomBox *Option18 SDCard".
  **FAIL** Missing choice *Option18 SDCard in UIConstraints "*Option18 
SDCard *KCCollate CustomBox".
WARN Datei einthält gemischt CR, LF, und CR LF Zeilenmenden.
WARN Size "A5" should be "149x210mm".
WARN Size "A6" should be "105x149mm".
WARN Size "B6" should be "128x182mm".
WARN Size "OficioII" should be the Adobe standard name 
"FanFoldGermanLegal".
WARN Size "P16K" should be "7,75x10,75".
WARN Size "OficioMX" should be the Adobe standard name "Oficio".
--

This seems to be from a manufacturer-supplied PPD file. The auto-
generated ones do not have "UIConstraints" lines. They also do not
contain mixed line ends.

Also sorry for giving you a wrong "ipptool" command line. Please run the
command line

ipptool -tv ipp://KM15881D.local:631/ipp/print get-printer-
attributes.test > ~/attrs.txt

The file get-printer-attributes-2.0.test only came with a later CUPS
version.

Please attach the attrs.txt file.

*.O files are generated by CUPS, to put the original version of a PPD
file when they change or replace it. Only the files without ".O" are
relevant for their print queue.

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

Title:
  "driverless" printer workflow has bad usability/ is partly broken

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-02-19 Thread Till Kamppeter
Christian, where is the rest which you wanted to post the day after Jan
30?

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  "driverless" printer workflow has bad usability/ is partly broken

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1816191] Re: Printers partially recognizes network printer, but isn't able to even print a test page

2019-02-15 Thread Till Kamppeter
*** This bug is a duplicate of bug 1815307 ***
https://bugs.launchpad.net/bugs/1815307

** This bug has been marked a duplicate of bug 1815307
   ipp printer isn't shown automatically - adding it errors with a CUPS 
internal error

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

Title:
  Printers partially recognizes network printer, but isn't able to even
  print a test page

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813825] Re: "driverless" printer workflow has bad usability/ is partly broken

2019-01-30 Thread Till Kamppeter
First, driverless printers (automatically created queues for IPP
printers) can be generated by cups-browsed and by CUPS.

So as a first approach you could try to stop cups-browsed to see whether
you still get auto-created printers or not.

sudo systemctl stop cups-browsed

stops cu[ps-browsed and

sudo systemctl start cups-browsed

starts it again. Please tell whether this makes the auto-created printer
go away or whether it changes its behavior to the better or to the
worse.

Another point to investigate is the PPD file (/etc/cups/ppd/.ppd) of the auto-created printer. If it is not present or broken,
the GUI can misbehave. The PPD files are automatically generated based
on information polled from the printer via IPP. The IPP 2.x standards
require that the printer provides sufficient information.

Print queues auto-created by cups-browsed are full-featured CUPS queues
and are present all the time while the printer is turned on and cups-
browsed is running. So they have a PPD file all the time.

Print queues auto-created by CUPS do only temporarily appear. They are
created when a job is printed and they stay only for 1 minute after the
job finishes. These queues are created purely by CUPS, cups-browsed does
not need to be running.

So check the presence of

/etc/cups/ppd/Kyocera_ECOSYS_P6026cdn.ppd

Does it exist? Please attach it.

If it does not exist, run following command:

lp -d Kyocera_ECOSYS_P6026cdn ~/,bashrc

and post the screen output here. Does the job get printed?

Then immediately check the presence of

/etc/cups/ppd/Kyocera_ECOSYS_P6026cdn.ppd

Does it exist? Please attach it.

You can also check by yourself:

sudo cupstestppd /etc/cups/ppd/Kyocera_ECOSYS_P6026cdn.ppd

Does this give any FAILs? Please post the output here.

You can also display the options defined by a printer's PPD file via

lpoptions -p Kyocera_ECOSYS_P6026cdn -l

If the queue is a temporarily auto-created queue from CUPS you most
probably will need to run this command within 1 minute after printing.

You can list queues which CUPS would auto-generate on-demand via

lpstat -e

The queues listed here but not listed by

lpstat -v

are queues which CUPS creates on-demand.

A problem is that the GUIs often do not fully support such temporary,
on-demand queues. Therefore we keep cups-browsed on Ubuntu so that we
get permanent auto-generated queues.

Please also run the following command (printer must be turned on):

driverless

This will give you the printer's IPP URI as output. Please post it here.

ipptool -tv  get-printer-attributes-2.0.test > attrs.txt

Replace  by the URI you obtained with the "driverless" command and
attach the output file, attrs.txt to this bug report. This is the
information which gets polled from the printer to auto-generate the PPD
file.

Please do not compress and do not package together any of the files we
ask you to attach. Please attch them one-by-one, so that one can easily
read them out of the browser when reading this bug report. Thanks.

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

Title:
  "driverless" printer workflow has bad usability/ is partly broken

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777531] Re: No GUI error reason for when 'Clear All' button for printer jobs doesn't work

2018-12-12 Thread Till Kamppeter
Please also attach your file

/etc/apparmor.d/usr.sbin.cupsd

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

Title:
  No GUI error reason for when 'Clear All' button for printer jobs
  doesn't work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777531] Re: No GUI error reason for when 'Clear All' button for printer jobs doesn't work

2018-12-12 Thread Till Kamppeter
Does the command line equivalent

cancel -a

work?

Does the "Clear All" button work after

aa-complain cupsd


** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  No GUI error reason for when 'Clear All' button for printer jobs
  doesn't work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Till Kamppeter
Is your user account in the lpadmin group in /etc/group (this is default
for the first user created during installation)?

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

Title:
  Print settings present two distinct interfaces for adding printers

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1805438] Re: Print settings present two distinct interfaces for adding printers

2018-11-30 Thread Till Kamppeter
For cups-pk-helper problems we need appropriate log files, as Sebastien
already asked for.

For the buttons, the "Additional printer settings" is not for adding
printers but for getting into an advanced interface (system-config-
printer). Perhaps one could rename it into "Advanced printer settings"?

The "Add a printer..." in the center of the screen only appears if there
is no printer set up at all. The "Add" button at the top is always
there, to be able to add more printers when there is already at least
one set up. I do not know whether one could improve the design here. I
would leave this to the GUI experts.

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

Title:
  Print settings present two distinct interfaces for adding printers

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1801382] Re: printing complex documents does not reproduce screen image on paper

2018-11-02 Thread Till Kamppeter
Checked by myself now. Opened the original file with evince, opened the
print dialog and clicked the preview button. The preview already shows
the problem. So the problem already occurs before the job gets to CUPS.
It is a problem of evince and/or GTK. Moving ...

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

** Package changed: cups (Ubuntu) => evince (Ubuntu)

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  printing complex documents does not reproduce screen image on paper

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1700085] Re: Mouse cursor is tiny on HiDPI screens

2018-10-03 Thread Till Kamppeter
zhiwei (chenzhiwei), same for me. The cursor is now as large as I set it
by accessibility settings, but it is tiny in the snap version of
LibreOffice.

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

Title:
  Mouse cursor is tiny on HiDPI screens

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1794180] [NEW] gnome-control-center crashed with SIGABRT

2018-09-24 Thread Till Kamppeter
Public bug reported:

I tried to run g-c-c as root:

sudo gnome-control-center

and after some seconds it aborted, without opening its window.

If it is not made for running it as root it should exit with a decent
error message and not crash.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Mon Sep 24 21:31:33 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-02-07 (229 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
ProcCmdline: gnome-control-center
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 cc_shell_model_set_panel_visibility ()
 ()
 cc_wifi_panel_static_init_func ()
Title: gnome-control-center crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash cosmic need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGABRT

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

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

2018-09-10 Thread Till Kamppeter
** Also affects: hplip
   Importance: Undecided
   Status: New

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2018-08-20 Thread Till Kamppeter
I see as the only problem here that jobs are submitted with
PageSize=Custom.Letter.SM (and not PageSize=Letter.SM). This is most
probably a problem of the GTK print dialog.


** Changed in: cups-filters (Ubuntu)
   Status: New => Invalid

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1785509] [NEW] gnome-control-center crashed with SIGSEGV in gtk_widget_set_visible()

2018-08-05 Thread Till Kamppeter
Public bug reported:

I opened the Thunderbolt page in the GNOME Control Center hoping to get
a Lenovo USB-C Dock charging my Lenovo Thinkpad X1 Yoga. I clicked
"Unlock" at the top and after entering my password I got the crash.

Starting GCC again and trying the same thing again I did not get a crash
(but also not my laptop getting charged through the docking station).

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.29.90-1~ubuntu1
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  5 21:20:41 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-02-07 (179 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
ProcCmdline: gnome-control-center
SegvAnalysis:
 Segfault happened at: 0x7fe03f71f07d :  cmp
%rax,(%rdx)
 PC (0x7fe03f71f07d) ok
 source "%rax" ok
 destination "(%rdx)" (0x6974616572632f2f) not located in a known VMA region 
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_widget_set_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ()
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_widget_set_visible()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

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


** Tags: amd64 apport-crash cosmic need-amd64-retrace third-party-packages

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

Title:
  gnome-control-center crashed with SIGSEGV in gtk_widget_set_visible()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

2018-07-10 Thread Till Kamppeter
It seems that evince has supplied a wrong name for the paper size. See
these two lines in the error_log:

[...]
D [03/Jul/2018:12:22:01 -0700] [Job 489] argv[5]="InputSlot=Auto number-up=1 
MediaType=Plain PageSize=Custom.Letter.SM noCollate OutputMode=Normal 
ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:a6bdd000-69b3-313b-6cfc-def9b98a0769 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1530645721 
time-at-processing=1530645721"
[...]
D [03/Jul/2018:12:22:01 -0700] [Job 489] Ghostscript command line: gs -dQUIET 
-dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -dNOMEDIAATTRS -dShowAcroForm 
-sstdout=%stderr -sOutputFile=%stdout -sDEVICE=cups -sMediaType=Plain 
-sOutputType=0 -dDuplex -r600x300 -dMediaPosition=7 -dDEVICEWIDTHPOINTS=0 
-dDEVICEHEIGHTPOINTS=0 -dcupsBitsPerColor=8 -dcupsColorOrder=0 
-dcupsColorSpace=17 -scupsPageSizeName=Custom -I/usr/share/cups/fonts -c -f -_
[...]

The client has sent the job with a "PageSize=Custom.Letter.SM" attribute
and it should have used "Letter.SM". In the second line you see that in
the Ghostscript command line zero got inserted for the width and the
height of the page, due to the broken page size name.

This is a bug of the client. As it occurs with evince it is most
probably the print dialog of GTK. Adding GTK task ...



** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: cups-filters (Ubuntu)
   Importance: High => Low

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1053891] Re: GTK print dialog does not allow printing and does not show options of a remote DNS-SD/Bonjour printer

2018-05-02 Thread Till Kamppeter
GNOME upstream bug #684533 has been moved to GitLab

https://gitlab.gnome.org/GNOME/gtk/issues/407

but it seems that GitLab is not yet supported by Launchpad, the link in
the GTK+ upstream task of this bug report cannot be replaced by this
one.

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

Title:
  GTK print dialog does not allow printing and does not show options of
  a remote DNS-SD/Bonjour printer

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755514] Re: Clicking the "Additional Printer Settings…" button launches system-config-printer multiple times

2018-03-27 Thread Till Kamppeter
** Changed in: system-config-printer (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1755514

Title:
  Clicking the "Additional Printer Settings…" button launches system-
  config-printer multiple times

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755514] Re: Clicking the "Additional Printer Settings…" button launches system-config-printer multiple times

2018-03-27 Thread Till Kamppeter
For me it looks like a bug in gnome-control-center.

When clicking the button, it should be checked whether there is already
a system-config-printer process running. If so, the window of it should
be pulled to the front, if not, s-c-p should get started.

In addition, it must be made sure that the button action happens only
once when one clicks the button once, and not repeatedly as long as the
button is held down. The reports of some users that they get 7 instances
of s-c-p with a single click on the button looks like that in the few
milliseconds while they have the left mouse button down the action of
starting s-c-p is repeated in quick frequence.

So these issues need to get fixed in g-c-c.

** Changed in: gnome-control-center (Ubuntu)
 Assignee: Till Kamppeter (till-kamppeter) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1755514

Title:
  Clicking the "Additional Printer Settings…" button launches system-
  config-printer multiple times

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1745674] [NEW] gsd-print-notifications crashed with SIGSEGV in process_new_notifications()

2018-01-26 Thread Till Kamppeter
Public bug reported:

I have created a print queue by the command line, via

lpadmin -p evtest -E -v ipp://192.168.0.51:631/ipp/print -m everywhere

This usually generates a notification that a new printer was added.
Instead, I got this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.26.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Jan 26 20:54:10 2018
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2015-04-30 (1002 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 cups_finalize_client_conf (cc=0x7fcef520) at usersys.c:1051
 _cupsSetDefaults () at usersys.c:924
 ()
 ()
 ()
Title: gsd-print-notifications crashed with SIGSEGV in 
cups_finalize_client_conf()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash bionic third-party-packages

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

Title:
  gsd-print-notifications crashed with SIGSEGV in
  process_new_notifications()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1745384] [NEW] gnome-control-center crashed with SIGABRT in mem_error()

2018-01-25 Thread Till Kamppeter
Public bug reported:

Crash happened when adding a printer, the HP OfficeJet Pro 8730. It
happened exactly when clicking the printer's entry from the discovered
printers in the printer tool of the g-c-c.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.26.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jan 25 10:46:50 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2015-04-30 (1001 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 mem_error (format=format@entry=0x7f89900c8b4d "assertion failed: %s") at 
../../../../glib/gslice.c:1472
 slab_allocator_free_chunk (chunk_size=chunk_size@entry=16, mem=) at ../../../../glib/gslice.c:1354
 private_thread_memory_cleanup (data=0x7f89440008c0) at 
../../../../glib/gslice.c:785
 __nptl_deallocate_tsd () at pthread_create.c:301
 __nptl_deallocate_tsd () at ../sysdeps/unix/sysv/linux/exit-thread.h:36
Title: gnome-control-center crashed with SIGABRT in mem_error()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

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

Title:
  gnome-control-center crashed with SIGABRT in mem_error()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-20 Thread Till Kamppeter
Patch to apply is the one of comment #53.

** Changed in: cups (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: cups-pk-helper (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-20 Thread Till Kamppeter
It is working now. Thank you very much.

Can someone upload this version of cups-pk-helper to Bionic? Thanks.

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-20 Thread Till Kamppeter
I have tried the PPA some days ago (Dec 15) and it did not work. Is
there a new version on the PPA?

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-20 Thread Till Kamppeter
shemgp, thank you also for this attempt but it is also not working for
me.

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-15 Thread Till Kamppeter
shemgp, unfortunately, your newest patch still does not solve the
problem for me.

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-14 Thread Till Kamppeter
I use Artful and I have added your PPA now. I have also removed "root"
as member of the "lpadmin" group in /etc/group, to have only your fix
active.

What did you change in your PPA compared to your patch from comment #36?

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-13 Thread Till Kamppeter
If I add "root" as member of the "lpadmin" group in /etc/group, all is
working perfecty: Kill button of the job list entry, "Clear all" at the
top of job list, and "Restart" in the print queue entry.

OdyX, WDYT? Should we add root as member of the lpadmin group?

shemgp, your latest patch is still not working for me, see comment #42.

Unsubscribing ubuntu-sponsors, as cups-pk-helper patch does not solve
the problem.

** Changed in: cups-pk-helper (Ubuntu)
   Status: Triaged => Incomplete

** Changed in: cups (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-13 Thread Till Kamppeter
I have applied the patch of comment #36 to cups-pk-helper now (nothing
uploaded, only local testing) and for me it does not work.

On the command line I have disabled a print queue and send a job to it,
by disabling the job stays in the queue so that one has time to do the
actual test.

Now I have started gnome-control-center and opened the section
"Devices"/"Printers". The queue I have stopped is shown as such and it
is also shown that it has one job. I clicked the "1 job" button to open
the job viewer. There are pause and kill buttons in the job line and a
"Clear all" button at the top. Neither with the kill button nor with the
"Clear all" button I can remove the jobe. I also cannot re-enable the
queue via the "Restart" in the print queue list.

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-13 Thread Till Kamppeter
"Restart" button for the queue returns to work when I re-install the
original cups-pk-helper without the patch.

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-13 Thread Till Kamppeter
Added cups-pk-helper task and re-subscribed ubuntu-sponsors.

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-12-13 Thread Till Kamppeter
So then why does no one apply the patch of comment #36? OdyX (printing
maintainer for Debian) and me, we are OK with this solution.


** Changed in: cups (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: cups-pk-helper (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cups-pk-helper (Ubuntu)
   Status: New => Triaged

** Changed in: cups-pk-helper (Ubuntu)
   Importance: Undecided => High

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1700092] Re: Text is tiny on HiDPI screens

2017-10-24 Thread Till Kamppeter
I opened gedit again today and the text size was OK. Was some change
done on it?

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

Title:
  Text is tiny on HiDPI screens

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721839] Re: Services asked for by UDEV do not get triggered

2017-10-16 Thread Till Kamppeter
Reported this bug upstream:

https://github.com/systemd/systemd/issues/7109

** Bug watch added: github.com/systemd/systemd/issues #7109
   https://github.com/systemd/systemd/issues/7109

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/7109
   Importance: Unknown
   Status: Unknown

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

Title:
  Services asked for by UDEV do not get triggered

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723462] Re: GNOME: Universal Access - Larger mouse cursor only works with GDM not with LightDM and with GDM inconsistent

2017-10-13 Thread Till Kamppeter
** Summary changed:

- GNOME: Universal Access - Larger mouse cursor only works with GDM not with 
LightDM and with GDM inconsistennt
+ GNOME: Universal Access - Larger mouse cursor only works with GDM not with 
LightDM and with GDM inconsistent

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

Title:
  GNOME: Universal Access - Larger mouse cursor only works with GDM not
  with LightDM and with GDM inconsistent

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723462] [NEW] GNOME: Universal Access - Larger mouse cursor only works with GDM not with LightDM and with GDM inconsistennt

2017-10-13 Thread Till Kamppeter
Public bug reported:

I have a vision problem and due to this I do not see very well the mouse
pointer in its original size on my 14" HiDPI 2560x1440 QHD screen of my
laptop. Therefore I go to "Universal Access" in the GNOME Settings and
choose "Medium" for "Cursor Size".

Due to bug 1722988 I happened to temporarily use GDM instead of LightDM
and so I observed that my cursor size change is only applied if I am
running my system with GDM as the greeter. With LightDM the cursor stays
in original size all the time. So I have currently switched to GDM again
to be able to have the larger mouse cursor.

The commmands I have used (as of comment #9 of bug 1722988):

--
sudo systemctl disable lightdm
sudo systemctl stop lightdm
sudo systemctl enable gdm #Seems to fail
sudo systemctl start gdm
sudo dpkg-reconfigure gdm3 #Shows lightdm selected
select gdm3, push enter

Reboot
--

But the large mouse cursor with GDM is also not perfect, as in some
situations it stays in the small size.

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Status: New

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

Title:
  GNOME: Universal Access - Larger mouse cursor only works with GDM not
  with LightDM and with GDM inconsistennt

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723446] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-10-13 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Oct 13 10:58:55 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (897 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.20 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f909a6615a9:  mov0x18(%rax),%rax
 PC (0x7f909a6615a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722690] [NEW] gnome-shell crashed with signal 5

2017-10-10 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Oct 10 21:37:28 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2015-04-30 (895 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gnome-shell crashed with signal 5

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722630] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-10-10 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 10 16:16:16 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (894 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.2 /org/gtk/gvfs/exec_spaw/8
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7ffb90d1c5a9:  mov0x18(%rax),%rax
 PC (0x7ffb90d1c5a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722366] [NEW] gnome-shell crashed with signal 5

2017-10-09 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Oct  9 11:23:33 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2015-04-30 (893 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gnome-shell crashed with signal 5

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721839] [NEW] Services asked for by UDEV do not get triggered

2017-10-06 Thread Till Kamppeter
Public bug reported:

The packages system-config-printer-udev and ippusbxd are installed,
having the following UDEV rule files:

/lib/udev/rules.d/70-printers.rules

--
# Low-level USB device add trigger
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
# Low-level USB device remove trigger
ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
--

/lib/udev/rules.d/55-ippusbxd.rules

--
# ippusbxd udev rules file

ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
--

If I turn on an appropriate printer (USB, supporting IPP-over-USB, here
the HP DeskJet 2540) I get in the output of "udevadm monitor
--environment"

--
UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
ACTION=add
BUSNUM=002
DEVNAME=/dev/bus/usb/002/033
DEVNUM=033
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
DEVTYPE=usb_device
DRIVER=usb
ID_BUS=usb
ID_MODEL=Deskjet_2540_series
ID_MODEL_ENC=Deskjet\x202540\x20series
ID_MODEL_ID=c211
ID_REVISION=0100
ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
ID_SERIAL_SHORT=BR54BFB02C05XK
ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
ID_VENDOR=HP
ID_VENDOR_ENC=HP
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
ID_VENDOR_ID=03f0
MAJOR=189
MINOR=160
PRODUCT=3f0/c211/100
SEQNUM=9891
SUBSYSTEM=usb
SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
TAGS=:udev-configure-printer:systemd:
TYPE=0/0/0
USEC_INITIALIZED=17527513940

UDEV  [17527.517724] add  /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 
(usb)
.MM_USBIFNUM=00
ACTION=add
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
DEVTYPE=usb_interface
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
INTERFACE=255/204/0
MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
PRODUCT=3f0/c211/100
SEQNUM=9892
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=17527517478

UDEV  [17527.522565] add  /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 
(usb)
.MM_USBIFNUM=02
ACTION=add
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
DEVTYPE=usb_interface
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
INTERFACE=255/4/1
MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02
PRODUCT=3f0/c211/100
SEQNUM=9895
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=17527522332

UDEV  [17527.523761] add  /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 
(usb)
.MM_USBIFNUM=01
ACTION=add
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
DEVTYPE=usb_interface
DRIVER=usblp
ID_VENDOR_FROM_DATABASE=Hewlett-Packard
INTERFACE=7/1/2
MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01
PRODUCT=3f0/c211/100
SEQNUM=9893
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=17527523500

UDEV  [17527.527275] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc)
.MM_USBIFNUM=01
ACTION=add
DEVNAME=/dev/usb/lp1
DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1
MAJOR=180
MINOR=1
SEQNUM=9894
SUBSYSTEM=usbmisc
USEC_INITIALIZED=17527527175
--

Here one can see that the UDEV rules files are correct, leading to the
correct systemd services being requested

SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service printer.target

but neither the service ippusbxd@002:033.service nor the service udev-
configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service
get started (note that I have put the .service file for ippusbxd in
place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service
/lib/systemd/system/").

I can start each of these services manually though:

sudo systemctl start 'udev-configure-printer@-devices-
pci:00-:00:14.0-usb2-2\x2d2.service'

sudo systemctl start ippusbxd@002:033.service

In each case ippusbxd gets started for this printer and a print queue
auto-created.

What I expect is that the services get automatically started (and that
worked in 17.04) so that after plugging in an USB printer I can
immediately print as the print queue gets created automatically.

The "udev-configure-printer..." service works for all USB printers, not
only IPP-over-USB (it automatically recognizes the printer typ and does
an appropriate setup).

This is a regression as we had always automatic setup of USB printers.

** Affects: systemd (Ubuntu)
 Importance: Critical
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.lau

[Bug 1721671] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-10-05 Thread Till Kamppeter
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct  5 20:27:09 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (889 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/16
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7fd86719c5a9:  mov0x18(%rax),%rax
 PC (0x7fd86719c5a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1718083] Re: UIFe: Add Additional Printer Settings button

2017-09-18 Thread Till Kamppeter
** Description changed:

  Impact
  ==
- The Ubuntu Desktop Team would like to add a button to the Settings app 
(gnome-control-center) named Additional Printer Settings that will open 
system-config-printer. system-config-printer has been part of the Ubuntu 
default install for years.
+ The Ubuntu Desktop Team would like to add a button to the "Printers" part of 
the Settings app (gnome-control-center) named "Additional Printer Settings" 
that will open system-config-printer. system-config-printer has been part of 
the Ubuntu default install for years.
  
  Justification
  ==
  The GNOME integrated Printer Settings is nice but it still misses a few 
settings that were easily configurable in Ubuntu 17.04. The most prominent 
missing settings is Printer Sharing. See GNOME upstream bug 
https://bugzilla.gnome.org/692532
  
  Hopefully, we can drop the button before 18.04 LTS is released.
  
  Notifications
  =

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

Title:
  UIFe: Add Additional Printer Settings button

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1718080] [NEW] gnome-control-center crashed with SIGSEGV

2017-09-18 Thread Till Kamppeter
Public bug reported:

Crashed when clicking the button "Manage Installed Languages" in the
"Region & Language" part of GNOME Settings.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 18 22:07:57 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2015-04-30 (873 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f12fead4499:  cmpq   $0x0,0x58(%rax)
 PC (0x7f12fead4499) ok
 source "$0x0" ok
 destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libnm.so.0
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1717736] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-09-16 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.34.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Sep 16 18:15:29 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (870 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7fd57c2935a9:  mov0x18(%rax),%rax
 PC (0x7fd57c2935a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1714359] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-08-31 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.33.91-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Aug 31 16:59:37 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (854 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7ff9e96b85a9:  mov0x18(%rax),%rax
 PC (0x7ff9e96b85a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1713152] [NEW] gsd-print-notifications crashed with SIGSEGV

2017-08-25 Thread Till Kamppeter
Public bug reported:

Happened when creating a CUPS queue.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.24.3-0ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Aug 25 16:41:57 2017
Disassembly: => 0x1ea86:Cannot access memory at address 0x1ea86
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2015-04-30 (848 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1ea86: Cannot access memory at address 0x1ea86
 PC (0x0001ea86) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ()
 _cupsGlobals () at globals.c:89
 ippNew () at ipp.c:2706
 ippNewRequest (op=IPP_OP_GET_NOTIFICATIONS) at ipp.c:2758
 ()
Title: gsd-print-notifications crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gsd-print-notifications crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1713058] [NEW] gsd-print-notifications crashed with SIGSEGV

2017-08-25 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.24.3-0ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Aug 25 09:53:41 2017
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2015-04-30 (848 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libcups.so.2
 http_send (http=0x7f5dd400dae0, request=548467168, uri=0x7f5dd400d100 
"P\265\303", ) at http.c:4364
 ()
 ()
 ()
Title: gsd-print-notifications crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-crash artful third-party-packages

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

Title:
  gsd-print-notifications crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1712875] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-08-24 Thread Till Kamppeter
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.33.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Aug 24 13:37:31 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (847 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f0e186b6569:  mov0x18(%rax),%rax
 PC (0x7f0e186b6569) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1712216] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-08-21 Thread Till Kamppeter
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.33.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Aug 21 19:12:39 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (844 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/9
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f29de7cd569:  mov0x18(%rax),%rax
 PC (0x7f29de7cd569) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1710896] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-08-15 Thread Till Kamppeter
Public bug reported:

As usual, when having Android phone connected to charge battery.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.33.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Aug 15 10:54:00 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (838 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f6ed3b95569:  mov0x18(%rax),%rax
 PC (0x7f6ed3b95569) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1710897] [NEW] emacs25-x crashed with SIGABRT in raise()

2017-08-15 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: emacs25 25.2+1-5
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Aug 15 11:18:28 2017
ExecutablePath: /usr/bin/emacs25-x
InstallationDate: Installed on 2015-04-30 (838 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: emacs cupsfilters/colormanager.c
Signal: 6
SourcePackage: emacs25
StacktraceTop:
 raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51
 ()
 ()
 ()
 ()
Title: emacs25-x crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

** Information type changed from Private to Public

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

Title:
  emacs25-x crashed with SIGABRT in raise()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1700085] Re: Mouse cursor is tiny on HiDPI screens

2017-08-12 Thread Till Kamppeter
There is no way to adjust scaling in current Ubuntu Artful.

It has disappeared from gnome-tweaks-tool and did not get added to
gnome-settings.

My suggestion for the right place for scaling is the "Displays" section
of gnome-settings. There there should be a widget for entering a scaling
value (non-integer) in each Display's configuration dialog (so that you
can also adjust displays with different resolution to fit together).

Back to this bug report, the mouse pointer ideally gets pre-scaled by
the scaling factor for the display and in the mouse settings the user
can enter a scaling factor to adjust it to his needs. Could we do it
this way?

As a workaround for the time being I selected the "Redglass" mouse
cursor theme in gnome-tweak-tool as the (too small) red cursor is more
visible than the (too small) black cursor.

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

Title:
  Mouse cursor is tiny on HiDPI screens

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1706097] Re: gvfsd-mtp crashed with SIGSEGV

2017-08-11 Thread Till Kamppeter
** Description changed:

- .
+ I get this every day when I have connected my Android phone for charging
+ its battery.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:29:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (816 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
-  LANG=en_US.UTF-8
-  LANGUAGE=en_US
-  PATH=(custom, user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  LANGUAGE=en_US
+  PATH=(custom, user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  SegvAnalysis:
-  Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
-  PC (0x7fea768b6cc9) ok
-  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
+  PC (0x7fea768b6cc9) ok
+  source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
-  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
+  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

** Changed in: gvfs (Ubuntu)
   Importance: Medium => Critical

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1708015] [NEW] systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()

2017-08-01 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 233-8ubuntu3
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Tue Aug  1 15:48:06 2017
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2015-03-25 (860 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-logind
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait () from /lib/systemd/libsystemd-shared-233.so
 sd_event_run () from /lib/systemd/libsystemd-shared-233.so
 ?? ()
 __libc_start_main (main=0x55e6bf033180, argc=1, argv=0x7ffd193c04c8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd193c04b8) at ../csu/libc-start.c:291
Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-yakkety
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-yakkety
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1706837] [NEW] systemd-journald crashed with SIGABRT in error_tail()

2017-07-26 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 233-8ubuntu3
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Wed Jul 26 21:03:54 2017
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2015-03-25 (854 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 error_tail (status=0, errnum=0, message=0x1 , args=0x87baad0551274a00) at error.c:267
 sd_event_run () from /lib/systemd/libsystemd-shared-233.so
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libgpg-error.so.0
Title: systemd-journald crashed with SIGABRT in error_tail()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-yakkety
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-yakkety
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in error_tail()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1706097] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-07-24 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jul 24 11:29:55 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (816 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7fea768b6cc9:  mov0x18(%rax),%rax
 PC (0x7fea768b6cc9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1705872] [NEW] systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

2017-07-22 Thread Till Kamppeter
*** This bug is a duplicate of bug 1605307 ***
https://bugs.launchpad.net/bugs/1605307

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 233-8ubuntu3
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
Date: Sat Jul 22 13:23:44 2017
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2015-03-25 (850 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-resolved
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait () from /lib/systemd/libsystemd-shared-233.so
 sd_event_run () from /lib/systemd/libsystemd-shared-233.so
 sd_event_loop () from /lib/systemd/libsystemd-shared-233.so
 ?? ()
Title: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-yakkety
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-yakkety
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-crash artful

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

Title:
  systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1705870] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

2017-07-22 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: udev 233-8ubuntu3
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CustomUdevRuleFiles: 80-net-setup-link.rules
Date: Sat Jul 22 00:19:41 2017
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2015-03-25 (849 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-udevd
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x558cc4bc3f20, argc=1, argv=0x7ffe6962b198, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe6962b188) at ../csu/libc-start.c:291
Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-yakkety
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-yakkety
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-crash artful need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1697207] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1693390] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
** This bug is no longer a duplicate of private bug 1689770

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1694041] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1697295] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1698716] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1697951] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1701846] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1699327] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1703385] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1702115] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1703145] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1699939] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1701844] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1700956] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1703219] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1704136] Re: gvfsd-mtp crashed with SIGSEGV

2017-07-16 Thread Till Kamppeter
*** This bug is a duplicate of bug 1693390 ***
https://bugs.launchpad.net/bugs/1693390

** This bug is no longer a duplicate of private bug 1689770
** This bug has been marked a duplicate of bug 1693390
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1704136] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-07-13 Thread Till Kamppeter
*** This bug is a duplicate of bug 1689770 ***
https://bugs.launchpad.net/bugs/1689770

Public bug reported:

Again, when plugging my phone.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Jul 13 09:22:35 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (805 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f3bf06b4cc9:  mov0x18(%rax),%rax
 PC (0x7f3bf06b4cc9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-07-11 Thread Till Kamppeter
Thanks for the quick fix.

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-07-11 Thread Till Kamppeter
OdyX, WDYT about applying the patch of comment #24 to the Debian/Ubuntu
package of CUPS? It adds root to CUPS' system group and this way cups-
pk-helper (runs as root) can authenticate queue and job manipulations
from GUIs.

If there are any objections from the Debian side, what about letting
only Ubuntu builds include root in the system group?

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 934291] Re: Deleting or stopping print jobs does not work

2017-07-11 Thread Till Kamppeter
shemgp, did you test this patch?

There is no user "lpadmin". With "run as lpadmin" I mean run as a user
which is in the lpadmin group.

So the better solution would be to build CUPS with root in the system
group or let root be member of the lpadmin group.

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

Title:
  Deleting or stopping print jobs does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1703385] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-07-10 Thread Till Kamppeter
Public bug reported:

Again when plugging my phone.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jul 10 10:27:54 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (802 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7faed9620cc9:  mov0x18(%rax),%rax
 PC (0x7faed9620cc9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1703145] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-07-08 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Jul  8 12:40:42 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (800 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7fe004a03cc9:  mov0x18(%rax),%rax
 PC (0x7fe004a03cc9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1702115] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-07-03 Thread Till Kamppeter
Public bug reported:

As usual, when I plugged my Android phone.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jul  3 11:31:00 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (795 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7fb8efddecc9:  mov0x18(%rax),%rax
 PC (0x7fb8efddecc9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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


** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


  1   2   3   4   5   6   7   8   9   10   >