On 28 June 2013 16:17, Iain Lane i...@orangesquash.org.uk wrote:
I'm guessing you got that from the changes file (or Launchpad's view of
it)? Those aren't quite the same as Debian changelogs, although
obviously they are parsed from them.
Yes, from Launchpad. I see. Ok.
--
You received
Public bug reported:
The changelog entry for 2.37.3-1ubuntu1 is unterminated [1], flowing in
to the next entry for the unreleased debian changes. The following does
not conform to changelog format as defined by debian-policy [2]:
glib2.0 (2.37.3-1ubuntu1) saucy; urgency=low
* Resynchronise
** Changed in: adobe-flashplugin (Ubuntu)
Status: Confirmed = New
** Changed in: bash (Ubuntu)
Status: Confirmed = New
** Changed in: dbus (Ubuntu)
Status: Confirmed = New
** Changed in: gegl (Ubuntu)
Status: Confirmed = New
** Changed in: gnome-games (Ubuntu)
Is there a way how i can run this trigger in some kind of
debug mode for having logging messages?
The trigger executes only one command, you can invoke it manually without
--quiet to see if it behaves similar:
# gtk-update-icon-cache --force --quiet /usr/share/icons/hicolor
(and/or
The delay here might not be due to any bug at all. Reassigned to gtk+
packages for their maintainers to determine.
Florian, which version of libgtk2.0-bin and libgtk-3-bin are you using?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
*** This bug is a duplicate of bug 1071565 ***
https://bugs.launchpad.net/bugs/1071565
** This bug has been marked a duplicate of bug 1071565
delete button does not delete anything
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
*** This bug is a duplicate of bug 871083 ***
https://bugs.launchpad.net/bugs/871083
** This bug has been marked a duplicate of bug 871083
gzip -9n sometimes generates a different output file on different
architectures
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 871083 ***
https://bugs.launchpad.net/bugs/871083
** This bug is no longer a duplicate of bug 899316
package gtk2-engines-pixbuf 2.24.8-0ubuntu1 failed to install/upgrade:
'./usr/share/doc/gtk2-engines-pixbuf/NEWS.gz' is different from the same file
on
*** This bug is a duplicate of bug 871083 ***
https://bugs.launchpad.net/bugs/871083
** This bug is no longer a duplicate of bug 899316
package gtk2-engines-pixbuf 2.24.8-0ubuntu1 failed to install/upgrade:
'./usr/share/doc/gtk2-engines-pixbuf/NEWS.gz' is different from the same file
on
*** This bug is a duplicate of bug 871083 ***
https://bugs.launchpad.net/bugs/871083
** This bug is no longer a duplicate of bug 899316
package gtk2-engines-pixbuf 2.24.8-0ubuntu1 failed to install/upgrade:
'./usr/share/doc/gtk2-engines-pixbuf/NEWS.gz' is different from the same file
on
*** This bug is a duplicate of bug 871083 ***
https://bugs.launchpad.net/bugs/871083
** This bug has been marked a duplicate of bug 871083
gzip -9n sometimes generates a different output file on different
architectures
--
You received this bug notification because you are a member of
** No longer affects: cdparanoia (Ubuntu)
** No longer affects: cdparanoia (Ubuntu Precise)
** No longer affects: cdparanoia (Ubuntu Oneiric)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
** Also affects: cdparanoia (Ubuntu)
Importance: Undecided
Status: New
--
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/871083
Title:
gzip -9n sometimes generates a
*** This bug is a duplicate of bug 974934 ***
https://bugs.launchpad.net/bugs/974934
** This bug has been marked a duplicate of bug 974934
package libappindicator0.1-cil 0.4.92-0ubuntu1 failed to install/upgrade:
ErrorMessage: dependency problems - leaving unconfigured
--
You received
*** This bug is a duplicate of bug 899316 ***
https://bugs.launchpad.net/bugs/899316
** This bug has been marked a duplicate of bug 899316
package gtk2-engines-pixbuf 2.24.8-0ubuntu1 failed to install/upgrade:
'./usr/share/doc/gtk2-engines-pixbuf/NEWS.gz' is different from the same file
On 20 September 2012 18:29, Sworddragon 819...@bugs.launchpad.net wrote:
Are you sure that this is the correct behavior?
Yes.
Some time before I have
opened this ticket it worked like expected: If I have started an
application in the background I could close the terminal without closing
the
On 20 September 2012 19:17, Sworddragon 819...@bugs.launchpad.net wrote:
I don't know it but with nohup the process will be a direct child of
init after closing the terminal.
If so then do not use nohup for this purpose.
--
You received this bug notification because you are a member of Ubuntu
On 20 September 2012 19:48, Sworddragon 819...@bugs.launchpad.net wrote:
So there is no difference for me.
My mistake then.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Comment #1 is correct. This is the intended behaviour of the system.
When you start a process it is always as a child of another, usually
some session. Graphically, you log in to a desktop session. When you
start gnome-terminal you are beginning a separate shell session and any
programs
The same problem appears in LXTerminal too. Maybe a
shared component is affected by this problem.
FYI the shared component in this case is the shell (usually
/usr/bin/bash or similar) which is run by these terminal programs.
Processes started by a shell are (typically) terminated when that
Bug #376147 tracks the issue of gnome-terminal not warning that closing
the terminal will terminate background processes.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/819842
My problem is now fixed. I will try and explain what happened.
I had a broken soft link that was preventing me from doing
the updates. (as you can see in the term.log)
Changing symlinks in /usr/bin is user error.
The ValueError from the log is a safety check against such
a user error. Not a
22 matches
Mail list logo
