[Bug 1614806] Re: This package breaks "ark" rar support
I am affected by this bug as well. It's just an annoyance, but quite an annoying annoyance. Any chance for a fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614806 Title: This package breaks "ark" rar support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1614806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452405] Re: wmctrl cannot move windows into certain positions
The bug still exists in a freshly-updated 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452405 Title: wmctrl cannot move windows into certain positions To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1452405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452405] [NEW] wmctrl cannot move windows into certain positions
Public bug reported: Ubuntu version 15.04, Unity version 7.3.2+15.04.20150420-0ubuntu1 and wmctrl version 1.07-7. If I try to place a window in the top left of the desktop, with the command wmctrl -r :ACTIVE: -e 0,0,0,1240,1034, it'll instead place the window about 10 pixels to the right of the edge of the Unity launcher. Similarly, trying to place a window on the top right corner with wmctrl -r :ACTIVE: -e 1,1280,0,640,360, the window appears in the right X position, but it's also about 10 pixels below the Unity panel. However, wmctrl -r :ACTIVE: -e 1,1280,720,640,335 will place the window at the expected position. It's like it's expecting the launcher and panel to be bigger than they actually are. I have my launcher set to 32 pixel icons, and I set up the scale for menu and titlebars as 0.875 in SettingsDisplays, and my resolution is 1920x1080. Would love to know if there's any workaround or alternative way to place windows in specific spots via script. I tried xdotool but causes the same abnormal behavior. I confirmed xmctrl works in other desktops like KDE (both 4 and plasma 5) ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452405 Title: wmctrl cannot move windows into certain positions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1452405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 971147] Re: xdotool and wmctrl don't move and resize windows after they are (semi)maximized
I have a similar issue with wmctrl in 15.04. Trying to place a window in the top-left corner, right next to the launcher, doesn't work. wmctrl -r :ACTIVE: -e 1,0,0,1240,1034 will place the window about 5 pixels to the right no matter what. If I try to place a window on the top right corner wmctrl -r :ACTIVE: -e 1,1280,0,640,360 it's 5 pixels below where it should be. I can't find any explanation and I can confirm it works in other desktops. Other operations like wmctrl -r :ACTIVE: -e 1,1280,720,640,335 work as expected, though, it just seems to have something against the left edge and top edge. I am not sure if this is the right bug to post into, but they are pretty similar so they might be related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/971147 Title: xdotool and wmctrl don't move and resize windows after they are (semi)maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/971147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
I am affected by this after I upgraded to 12.10. Not a major issue but would like to know what it is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778627] Re: In natty, bash completion now quotes shell variable references rather than expanding them
I am also suffering this problem in Ubuntu 12.10. Commenting out the sourcing of bash-completion managed to fix it, but the problem is that it disables all of its advantages. The problem must be in one of the various files at /usr/share/bash-completion/completions ,I'd bet. But debugging that until finding the culprit would be a task of true patience. I tried to build bash manually and it always does the same thing unless I disable sourcing bash-completion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778627 Title: In natty, bash completion now quotes shell variable references rather than expanding them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/778627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768109] Re: python2.7 crashed with SIGSEGV
I also get this, but I couldn't get any debug information (crash is silent even in debug mode). I am glad someone reported it first with more relevant data. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768109 Title: python2.7 crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/kupfer/+bug/768109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 796076] Re: When run as root [gksudo gedit whatever] gedit tries to open a 2nd 'untitled document 1'
Anyone examined the .desktop file? If I drag it into the launcher bar, using the open new document/window functions work very oddly, opening more than one ghost document. If I try to add double quotes the %U, it tries to open $HOME/Documents (which is a folder, won't work). I can also reproduce the original bug. It's weird because when done manually, gedit seems to behave nicely if invoked from the command line, but seems to fail when the .desktop file is used. So maybe it has something to do with it. For example, if I run gedit and use the launcher shortcut to open a new document, it doesn't work (opens another window with ghost documents), but if I try from command line (gedit --new-document) , it'll open a new document as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/796076 Title: When run as root [gksudo gedit whatever] gedit tries to open a 2nd 'untitled document 1' To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/796076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849882] Re: krename crashed with SIGSEGV in __libc_csu_init()
I also get a crash. Tried to build it from source, and this is what
happened. Oneiric 32-bit, all packages up-to-date to this day.
(gdb) r
Starting program: /usr/bin/krename
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
QString (other=optimized out, this=0x81062ac) at
/usr/include/qt4/QtCore/qstring.h:729
729 { Q_ASSERT(other != this); d-ref.ref(); }
(gdb) bt
#0 QString (other=optimized out, this=0x81062ac)
at /usr/include/qt4/QtCore/qstring.h:729
#1 __static_initialization_and_destruction_0 (__priority=65535,
__initialize_p=1)
at /dev/shm/krename/src/plugin.cpp:22
#2 _GLOBAL__sub_I__ZN6Plugin17S_TOKEN_SEPARATORE () at
/dev/shm/krename/src/plugin.cpp:51
#3 0x080dd422 in __libc_csu_init ()
#4 0x01a890aa in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#5 0x080603e9 in _start ()
(gdb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849882
Title:
krename crashed with SIGSEGV in __libc_csu_init()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krename/+bug/849882/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849882] Re: krename crashed with SIGSEGV in __libc_csu_init()
This bug report from Redhat seems to have more about it. I tried this solution in the source and works. https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=684908 ** Bug watch added: Red Hat Bugzilla #684908 https://bugzilla.redhat.com/show_bug.cgi?id=684908 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849882 Title: krename crashed with SIGSEGV in __libc_csu_init() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krename/+bug/849882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
@Mark Mr.Shuttleworth, you clearly are a more successful person than I am, and I respect your opinions to a certain degree. I only want this change to be reverted since I work with regular end-users without computer knowledge and I am sure they will react to this change in a negative way. You seem to be either stubborn or very confident. I won't discuss this change further since, after all, it doesn't affect ME personally. I can change it, most of the persons posting here can, if they like it or not.. Just think of those who got Ubuntu installed by a friend or relative, the type of people vulnerable to phising scams and spyware infections. They need to be babysitted, to put it bluntly. Your adamant replies suggest me you do have something interesting in your mind, and I am certainly not the only one wanting to know what it is. You also imply you thought of the negative consequences, so you clearly thought of the non-tech users (which are after all, the largest numbers to handle). From my humble position I suggest a little insight on the things to come. Play your cards right and you might turn hatred into hype. Being an Ubuntu user, I am naturally inclined to see my distro of choice success. It's the same reason we want our team to win. -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
@Mark I think this is a very sensitive decision to take in a LTS release, considering how many users are unable/unwilling to learn how to change it. It will create that kind of frustration that is not critical but enough to create hatred to the brand. There are already several shortcomings/papercuts annoying non-technical users and this will be a big one. If the geek friend/employee is not there to fix it, the amount of complaints will be very big. Also, I would like to hear real explanations on the good reasons for the change. So far it seems just a mere let's be different decision. As for the usability behind it...well, you are just ignoring the usability studies that put the close buttons on the corners in the first place. Let's be clear, this decision doesn't affect ME, I am a KDE user and I am able to modify a simple theme. And as me, most of the concerned users here. But the problem is, as always, the masses. Ubuntu often gets installed by the geek friend to the average Joethink of the geek friends everywhere ;) We are worrying about the reaction of the masses because it will ultimately influence Ubuntu's view to the world. Whiners make much more noise than satisfied customers. Also, gconf is as valid as workaround as the registry is in Windows. It's an unfriendly, crude app that just works, and mistakes on it require fixing beyond the abilities of an Average Joe. Consider that as well if you want to go forward. Maybe you should go browser ballot screen on the users to give them a choice before starting. But the biggest problem here is the feeling of our calls for sanity seeming to fall in deaf ears. This is like a poker bluff. Be really sure you got good cards, or you might lose brand credibility and be labeled as just another evil megacorp. Once you get the stigma, you'll be forever evil even if you just make one mistake. -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
