Public bug reported:
Get this logged:
systemd[1]: privoxy.service: Control process exited, code=exited status=1
systemd[1]: Failed to start Privacy enhancing HTTP Proxy.
systemd[1]: privoxy.service: Unit entered failed state.
systemd[1]: privoxy.service: Failed with result 'exit-code'.
ProblemTy
[Expired for console-setup (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: console-setup (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.n
** Changed in: evince
Status: Confirmed => Unknown
--
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/1168978
Title:
Evince crashes consistently, reading 50+ pages into specific
drhc, again, this report is closed, so commenting here is a waste of
time. File a support request against whatever Ubuntu GUI you are using
as already previously requested (not continue to comment here in a
closed report).
--
You received this bug notification because you are a member of Ubuntu
D
Ok, but then why he does not say that it is an unstable version??
https://wiki.gnome.org/Apps/Evolution
I understand what you put me is the original source. I fully understand
the impossibility that they can not enter now working in the sector and
would not be safe to make the update now.
I hope
*** This bug is a duplicate of bug 1444580 ***
https://bugs.launchpad.net/bugs/1444580
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1444580, so is being marked as such.
** Changed in: gnome-disk-utility
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1479710
Title:
/usr/bin/gnome-
disks:11:g_dbus_obje
After last updates
This problem corrected.
We can close the job
Thanks
Ertan
** Changed in: nautilus (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpa
This bug was fixed in the package glib2.0 - 2.46.1-1
---
glib2.0 (2.46.1-1) unstable; urgency=medium
[ Michael Biebl ]
* Drop clean-la.mk from debian/rules, no longer required.
[ Iain Lane ]
* New upstream release 2.46.1
+ Remove system_header pragma (should fix lack of w
This bug was fixed in the package glib2.0 - 2.46.1-1
---
glib2.0 (2.46.1-1) unstable; urgency=medium
[ Michael Biebl ]
* Drop clean-la.mk from debian/rules, no longer required.
[ Iain Lane ]
* New upstream release 2.46.1
+ Remove system_header pragma (should fix lack of w
Thanks, but I said nothing about gnome-session-flashback.
I have no gnome-session-flashback and gnome-flashback package installed (also
I know nothing about them).
Instead I have the same result:
"4) What happens instead is it shows a gray static screen as per attached
screenshot."
regardless of
adrhc, as this report is closed, it has nothing to do with your problem.
If you have an issue with RDP'ing to Ubuntu while using gnome-session-
flashback, you either haven't configured it properly (more likely as I
can use Windows RDC to connect to Vivid using gnome-session-flashback
just fine), o
The problem is in gnome-terminal, affects Ubuntu and Ubuntu Gnome in
15.10 as of 17 Oct 2015. Unity is not involved.
** Also affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity
Status: New => Invalid
** Changed in: gnome-terminal (Ubuntu)
*** This bug is a duplicate of bug 1483868 ***
https://bugs.launchpad.net/bugs/1483868
** This bug is no longer a duplicate of bug 586528
keyboard doesn't work after screensaver shuts down the monitor
** This bug has been marked a duplicate of bug 1483868
keyboard doesn't work after xscr
*** This bug is a duplicate of bug 1483868 ***
https://bugs.launchpad.net/bugs/1483868
** This bug is no longer a duplicate of bug 586528
keyboard doesn't work after screensaver shuts down the monitor
** This bug has been marked a duplicate of bug 1483868
keyboard doesn't work after xscr
*** This bug is a duplicate of bug 1483868 ***
https://bugs.launchpad.net/bugs/1483868
You have opened bug report #1483868
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1483868 you
had been asked questions to complete your bug report, and to help find
out where exactly problem is
*** This bug is a duplicate of bug 586528 ***
https://bugs.launchpad.net/bugs/586528
** This bug has been marked a duplicate of bug 586528
keyboard doesn't work after screensaver shuts down the monitor
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
@Lysenko: FFS, there was somebody else commenting on this issues this
month. The bug is still the same, there is nothing else to add to this.
The reproduction scenario is still the same.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@Václav Haisman, this 3 bugs where reported in 2010, i have tested this
bug in 15.04 unity DE, there are no bug, if you have bug provide your
steps to reproduce otherwise this will be closed on Monday.
P.s. In 5 years in codebase of gnome-screensaver were a lot changes this
bug seems to be fixed w
** Changed in: evince
Status: New => Expired
--
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/1405912
Title:
Evince eats all CPU and all memory
To manage notifications about t
*** This bug is a duplicate of bug 1286294 ***
https://bugs.launchpad.net/bugs/1286294
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1286294, so is being marked as such.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I took the liberty of moving this bug report to the gimp package, since it
doesn't seem to be related to radiotray.
Do you consistently get this error message each time you attempt to run gimp?
Also, could you pl
You have been subscribed to a public bug:
GIMP was functioning normally then after restart received following error
launching GIMP:
Gtk-Message: Failed to load module "pantheon-filechooser-module" Bus error
(core dumped) gimp
Also received:
Gtk-Message: Failed to load module "canberra-gtk-modul
I got the same issue while creating a partition on a normal sata
connection.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1437921
Title:
gnome-disks crashed with SIGSE
@Lysenko: 22 people confirmed this. There are 2 duplicates attached to
this bug report and then there is #1483868 that I was requested to fill
separately. Yet, you want to close this bug. Are you for real? I have
nothing more to say, except expletives.
--
You received this bug notification becau
For the love of all that's holy... Please fix this because it is driving
me insane!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/797485
Title:
Status Bar Covers File Name at Bot
I have tested this yesterday, and i don't have this issue, may be
because i have 4 digit password on system i have tested on, and i'm
entering password on numpad?
gnome-screensaver: Installed: 3.6.1-0ubuntu16
Ubuntu 15.04, Unity DE
--
You received this bug notification because you are a member o
** Changed in: gnome-screensaver (Ubuntu)
Assignee: Abhishek solanki (abhisheksolanki18) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1507123
Title:
@Václav Haisman please provide clear steps for reproduce, otherwise i
will close this. Bug creator unsubscribe yesterday. If you will not, i
will close this in 2 days.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver i
Double click is not meant to select a URL (there's an option in the
right click menu for that), and adding colon to the list of word-chars
won't fix it either. E.g. if you have a URL with a trailing dot (which
strictly speaking could be a part of the URL, but usually denotes the
end of a sentence)
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for th
(In reply to Adrian Johnson from comment #80)
> (In reply to Albert Astals Cid from comment #70)
> > For the pdfsigverify it seems we kind of agreeed on the compromise to call
> > it pdfsig that only does verification right now but in the future may
> > suppport signing?
>
> This is the only thing
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for th
(In reply to Adam Reichold from comment #81)
> (In reply to Adrian Johnson from comment #78)
> > I agree that the two calls to doGetChars and updateHash should be merged but
> > I don't think a for loop is the best way to process loops where the
> > increment is not exactly the same on each iterati
(In reply to Andre Guerreiro from comment #76)
> Created attachment 118745 [details] [review]
> Incremental hashing + large file support
>
> With this patch I've implemented the incremental hashing plus the large file
> support.
>
> This is still untested with files larger than 2GB but is correct
(In reply to Adam Reichold from comment #81)
> (In reply to Adrian Johnson from comment #78)
> > I agree that the two calls to doGetChars and updateHash should be merged but
> > I don't think a for loop is the best way to process loops where the
> > increment is not exactly the same on each iterati
(In reply to Albert Astals Cid from comment #82)
> > - Is '-c' the best option name for "don't perform certificate validation"?
>
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
It's vital to put th
(In reply to Adrian Johnson from comment #80)
> (In reply to Albert Astals Cid from comment #70)
> > For the pdfsigverify it seems we kind of agreeed on the compromise to call
> > it pdfsig that only does verification right now but in the future may
> > suppport signing?
>
> This is the only thing
(In reply to Andre Guerreiro from comment #76)
> Created attachment 118745 [details] [review]
> Incremental hashing + large file support
>
> With this patch I've implemented the incremental hashing plus the large file
> support.
>
> This is still untested with files larger than 2GB but is correct
(In reply to Albert Astals Cid from comment #82)
> > - Is '-c' the best option name for "don't perform certificate validation"?
>
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
It's vital to put th
Public bug reported:
The keyboard doesn't work when I return to work on the computer after a
few minutes, long enough for the screen to go blank.
To reproduce:
Don't touch the keyboard nor mouse for a while.
After the first 5 minutes, the screensaver kicks in (matrix).
On minute 10, the screen go
FYI --- using command line to eject the disk/partiton do work, see
http://askubuntu.com/questions/422481/prevent-usb-drives-from-auto-
remounting-after-remove
On the other hand, I see surprising that this bug is marked Medium. For
non-tech-savy users, can ends in unclean disconnect and even data-l
Thanks for reporting.
It's probably too close to the release of 15.10 to risk introducing a
new version at this point, but hopefully someone will take a look at
this for the next release.
I noticed that 3.18 has been packaged in Debian unstable already, so
maybe it is simply a case of merging (or
** Changed in: evince
Importance: Medium => Critical
--
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/1436555
Title:
evince crashed with SIGSEGV in atk_object_notify_state_change()
This bug was fixed in the package gconf - 3.2.6-3ubuntu5
---
gconf (3.2.6-3ubuntu5) wily; urgency=medium
* Call dh_python3 with --shebang=/usr/bin/python3. LP: #1440549.
-- Matthias Klose Fri, 16 Oct 2015 16:34:16 +0200
** Changed in: gconf (Ubuntu)
Status: New => Fix Re
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1500673
** Changed in: evince
Status: Confirmed => Incomplete
--
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/1449700
Title:
evince crashed with SIGSEGV in add_range()
To manage noti
I am on 15.04. That it does not happen to you does not mean it does not
happen to others.
** Changed in: gnome-screensaver (Ubuntu)
Status: Invalid => Confirmed
** Changed in: xscreensaver (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are
** Changed in: gnome-screensaver (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1390270
Title:
Ubuntu 14.10 lockscreen
Please see in the screenshot:
1. Thin font in the clock.
2. An extra button (three horizontal lines) for bringing up the Menu in
Nautilus.
3. Thin font in Nautilus (filenames).
4. The correct font in System Settings.
EXPECTED:
A. Font in Nautilus should be the same as in System Settings.
B. Th
51 matches
Mail list logo
