[Bug 1269838] Re: gnome-session.log takes 8 GB in a few hours
@mpt yes, this is still an issue on Ubuntu 14.04LTS. My /home partition fills up nearly every day (bad on an SSD also because of write amplification). -rw-r- 3151151104 Feb 4 13:06 gnome-session-Unity.log The log spam is useuless repetive stuff like: (putty:29947): GLib-CRITICAL **: Source ID 67342 was not found when attempting to remove it [0x7f2468000ec8] v4l2 demux error: dequeue error: No such device [0x7f2468000ec8] v4l2 demux error: dequeue error: No such device [4757:4787:0204/130259:ERROR:connection.cc(1892)] Cookie sqlite error 13, errno 0: database or disk is full, sql: UPDATE cookies SET last_access_utc=? WHERE creation_utc=? ** Changed in: gnome-session (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1269838 Title: gnome-session.log takes 8 GB in a few hours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1269838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup
This seems to still be an issue: and it's a serious issue when a semi public computer is involved, as those using the computer won't know the password. It is also a problem to train users to enter their password when a prompt box comes up: that's just ripe for abuse. See also: http://askubuntu.com/questions/867/how-can-i-stop-being-prompted-to-unlock-the-default-keyring-on-boot --- Better and more secure the above cases is a mode for gnome-keyring "never prompt". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/575877 Title: gnome-keyring mysteriously asks for keyring password on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
Swap is the equivalent of main memory: the security issues are no different. Nobody can complain about swap written to disk, as that's a risk for any piece of main memory at any time. Why turn things so far upside down to support an edge case (infinite scrollback left open for long periods of time)? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
The oom killer will only come along if some epic long files have been cat'ed to the terminal, and infinite scrollback is selected. Speed, battery life, SSD life, energy use and privacy are all reasons to have the common case be no disk writes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
How do you think gnome-terminal should handle that? Suppose you have 4 GB of ram, shall it consume up to 3 GB and then starting using the disk? Sounds not only hard to implement, but also why should it take away RAM from other apps? The Linux virtual memory system is highly adept at swapping out content that's not in active use, keeping RAM for what's hot. The global system for this works quite well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
@Egmont wrote: Running out of disk space is much less likely and effects the system less badly than running out of RAM, and your RAM would eventually make it into the disk (swap) anyways. But I run out of ram space very rarely. It's highly elegant to keep volatile data in RAM unless RAM is full. -- @Egmont wrote: still don't think SSD lifetime is a valid real-life issue. My particular desktop SSD is at 19% lifetime (as measured by the vendor through SMART code 202 Perc_Rated_Life_Used or 173 Wear_Leveling_Count). So yes, real people can wear out an SSD. -- Aside from that writing to disk is dramatically more system overhead, compared to RAM. -- Bash history, which is NOT kept from overwriting, is a better use of disk writes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles
Here's output of sudo strace -p XX where X is the process ID
of the misbehaving gvfsd-afp:
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
And sudo gdb -p followed by bt
(gdb) bt
#0 0x7f766cb897eb in __libc_recv (fd=7, buf=0x23d86a0, n=16, flags=-1)
at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
#1 0x7f766d5e3bec in g_socket_receive_with_blocking ()
from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#2 0x7f766d5cb625 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#3 0x7f766d5cd02b in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x7f766d5cc28b in g_input_stream_read_async () from
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5 0x0040c0c1 in ?? ()
#6 0x7f766d5ccd5a in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7 0x7f766d5f08db in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8 0x7f766d5f08f9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9 0x7f766d05fce5 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f766d060048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f766d06030a in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x0040b7c1 in ?? ()
#13 0x00406b97 in ?? ()
#14 0x7f766c7d6ec5 in __libc_start_main (main=0x406b40, argc=4,
argv=0x7fff04eca8e8,
init=optimized out, fini=optimized out, rtld_fini=optimized out,
stack_end=0x7fff04eca8d8)
at libc-start.c:287
#15 0x00406bc9 in ?? ()
--
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/951585
Title:
gvfsd-afp consumes 100% of processor cycles
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles
(The prior backtrace is under Ubuntu 14.04LTS fully patched) gvfs Version: 1.20.1-1ubuntu1 -- 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/951585 Title: gvfsd-afp consumes 100% of processor cycles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
See also http://ubuntuforums.org/showthread.php?t=1830432 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430620] [NEW] gnome-terminal writes excessively to /tmp (affecting SSD drives)
Public bug reported: 1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus timestamps). 2) In another window cat a file to the screen. 3) Observe the activity. I see large churn on the /tmp partitition: 20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.170744 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.170744 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.171222 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.171222 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.171699 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.171699 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.172114 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.172114 gnome-terminal(23352): W /tmp/#132828 (deleted) 20:41:24.172298 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.172298 gnome-terminal(23352): W /tmp/#132835 (deleted) 20:41:24.172617
[Bug 865082] Re: gnome-terminal writes to /tmp on every line of output
Probably related, here's a small sample as captured by the new fatrace --filter W utility on Ubuntu 14.04 LTS: 09:35:01.577176 gnome-terminal(8923): RW /tmp/#132358 (deleted) 09:35:01.588323 gnome-terminal(8923): W /tmp/#132359 (deleted) 09:35:01.588323 gnome-terminal(8923): RW /tmp/#132359 (deleted) 09:35:01.588323 gnome-terminal(8923): W /tmp/#132358 (deleted) 09:35:01.588323 gnome-terminal(8923): RW /tmp/#132358 (deleted) 09:35:01.604411 gnome-terminal(8923): W /tmp/#132359 (deleted) 09:35:01.604411 gnome-terminal(8923): RW /tmp/#132359 (deleted) 09:35:01.604411 gnome-terminal(8923): W /tmp/#132358 (deleted) 09:35:01.604411 gnome-terminal(8923): RW /tmp/#132358 (deleted) 09:35:01.606859 bash(12220): CW /home/bnesbitt/.bash_history 09:35:01.606859 bash(12220): RCWO /home/bnesbitt/.bash_history 09:35:01.610768 gnome-terminal(8923): CW /tmp/#132355 (deleted) 09:35:01.610768 gnome-terminal(8923): CW /tmp/#132355 (deleted) 09:35:01.610856 gnome-terminal(8923): CW /tmp/#132356 (deleted) 09:35:01.610856 gnome-terminal(8923): CW /tmp/#132356 (deleted) 09:35:01.636285 gnome-terminal(8923): W /tmp/#132359 (deleted) 09:35:01.636285 gnome-terminal(8923): RW /tmp/#132359 (deleted) 09:35:01.636285 gnome-terminal(8923): W /tmp/#132358 (deleted) 09:35:01.636285 gnome-terminal(8923): RW /tmp/#132358 (deleted) 09:35:01.666355 gnome-terminal(8923): W /tmp/#132359 (deleted) 09:35:01.666355 gnome-terminal(8923): RW /tmp/#132359 (deleted) 09:35:01.666355 gnome-terminal(8923): W /tmp/#132358 (deleted) 09:35:01.666355 gnome-terminal(8923): RW /tmp/#132358 (deleted) 09:35:01.677547 gnome-terminal(8923): W /tmp/#132359 (deleted) 09:35:01.677547 gnome-terminal(8923): RW /tmp/#132359 (deleted) 09:35:01.677547 gnome-terminal(8923): W /tmp/#132358 (deleted) 09:35:01.677547 gnome-terminal(8923): RW /tmp/#132358 (deleted) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/865082 Title: gnome-terminal writes to /tmp on every line of output To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/865082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1372604] [NEW] Setting browser Default application ineffective (screenshot attached). Gnome.
Public bug reported: In Ubuntu 14.04LTS: In system settings there's a control for Default applications for Web. This does not appear to change the gnome-conf settings. See attached screenshot. Note how Firefox is shown in one place, Chrome in the other. This in turn leads to incorrect behavior when a program like an RSS reader, Skype or https://josm.openstreetmap.de/ wants to open a browser window to a particular URL. Usually I end up with a blank Chrome window, where I wanted a filled in Firefox window. ** Affects: evince (Ubuntu) Importance: Undecided Status: Invalid ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Attachment added: Selection_112.png https://bugs.launchpad.net/bugs/1372604/+attachment/4211743/+files/Selection_112.png ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: evince (Ubuntu) Status: New = Invalid ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- 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/1372604 Title: Setting browser Default application ineffective (screenshot attached). Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1372604/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 693852] Re: Decimal point on my numeric keyboard does not work. Is it because of regional settings?
*** This bug is a duplicate of bug 795985 *** https://bugs.launchpad.net/bugs/795985 Still true as of Ubuntu 12.04.4 LTS, with US English Locale and 101 Key Keyboard. Neither the numbers above the keyboard, nor the numeric pad . work. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/693852 Title: Decimal point on my numeric keyboard does not work. Is it because of regional settings? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/693852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251022] Re: Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take)
This is NOT a duplicate of #1079953 And 12.04 is a LTS support version, so a fix for 13.10 is not relevant. The proper URL for the stable release updates is https://wiki.ubuntu.com/StableReleaseUpdates The feature is completely broken in 12.04 LTS due tothe missing dependency. ** This bug is no longer a duplicate of bug 1079953 Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1251022 Title: Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
Using 12.04, fresh upgrade, fully patched: alacarte launches but clicking *Properties* or *New Item* results in a crash. Checking [x] report this error does nothing apparent. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1079953 Title: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
And pressing HELP gives: The URI ‘ghelp:user-guide?menu-editor#menu- editor’ does not point to a valid page. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1079953 Title: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251022] [NEW] Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take)
Public bug reported: While bug https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953 is closed, the issue persists. With alacarte 0.13.2-2ubuntu4 on Ubuntu 12.04, nothing works. Pressing *New Item* or *Properties* results in a crash. Checkbox actions don't take. And inexplicably [x] report an error does nothing. But here's a console exception: hardhat:~ alacarte Traceback (most recent call last): File /usr/share/alacarte/Alacarte/MainWindow.py, line 634, in on_properties_button_clicked self.on_edit_properties_activate(None) File /usr/share/alacarte/Alacarte/MainWindow.py, line 391, in on_edit_properties_activate process = subprocess.Popen(['gnome-desktop-item-edit', file_path], env=os.environ) File /usr/lib/python2.7/subprocess.py, line 679, in __init__ errread, errwrite) File /usr/lib/python2.7/subprocess.py, line 1249, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory ** Affects: alacarte (Ubuntu) Importance: Undecided Status: New ** Tags: 12.04 regression-update unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1251022 Title: Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1079953 Title: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819163] [NEW] 2 page eFax shows same data on each page
Public bug reported: I received a 2 page fax from eFax. In this application the fax shows as two pages, but both pages are identical copies of the first page. Gimp was able to view the second page without incident. The fax in question has private fiscal data. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: eog 2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CheckboxSubmission: e6c6b380b568460f212c72eb7de49c43 CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b Date: Mon Aug 1 00:56:21 2011 ExecutablePath: /usr/bin/eog InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi natty unity-2d -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/819163 Title: 2 page eFax shows same data on each page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/819163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 819163] Re: 2 page eFax shows same data on each page
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/819163 Title: 2 page eFax shows same data on each page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/819163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 658786] Re: Shadows not rotated on a vertical panel in Maverick
Still true in 11.04 the Natty Narwhal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. https://bugs.launchpad.net/bugs/658786 Title: Shadows not rotated on a vertical panel in Maverick -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 658786] Re: Shadows not rotated on a vertical panel in Maverick
Ubuntu 11.04 Natty Narwhal screenshot, showing improperly rotated panel. The GNOME Panel 2.30.2. Shadow is bad in Left and Right positions, and ok in Top and Bottom positions. ** Attachment added: Improper_Shadow_Rotation_Enlarged.png https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/658786/+attachment/1811300/+files/Improper_Shadow_Rotation_Enlarged.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. https://bugs.launchpad.net/bugs/658786 Title: Shadows not rotated on a vertical panel in Maverick -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
